-webkit-flex-flow does not work with inherit/initial values
https://bugs.webkit.org/show_bug.cgi?id=92709

Patch by Douglas Stockwell <dstockwell@chromium.org> on 2012-07-31
Reviewed by Ojan Vafai.

Source/WebCore:

Add a new handler for flex-flow and move flex to StyleBuilder to mirror the standard pattern for handling initial/inherit in shorthands.

Test: css3/flexbox/flex-flow-initial.html

* css/StyleBuilder.cpp:
(WebCore::StyleBuilder::StyleBuilder): Added handlers for flex and flex-flow.
* css/StyleResolver.cpp:
(WebCore::StyleResolver::collectMatchingRulesForList): Removed hand written logic for handling flex.

LayoutTests:

Test that flex-flow handles 'initial' as expected.

* css3/flexbox/flex-flow-initial-expected.txt: Added.
* css3/flexbox/flex-flow-initial.html: Added.

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@124297 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[Chromium] Update test expectations.
https://bugs.webkit.org/show_bug.cgi?id=85952
https://bugs.webkit.org/show_bug.cgi?id=92835

Unreviewed, test expectation updates.

* platform/chromium/TestExpectations:



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@124298 268f45cc-cd09-0410-ab3c-d52691b4dbfc
ColorInputType::typeMismatchFor is returning the opposite bool
https://bugs.webkit.org/show_bug.cgi?id=92836

Reviewed by Kent Tamura.

No new tests. Covered by color-suggestion-picker-appearance.html.

* html/ColorInputType.cpp:
(WebCore::ColorInputType::typeMismatchFor):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@124299 268f45cc-cd09-0410-ab3c-d52691b4dbfc
[Chromium][Mac] Assertion failure in null_audio_sink.cc running WebGL video layout test on 10.5 debug bots
https://bugs.webkit.org/show_bug.cgi?id=89529

Unreviewed gardening.

Should be mostly/all cured on Mac.  See http://crbug.com/138583 for ongoing details.


* platform/chromium/TestExpectations:


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@124300 268f45cc-cd09-0410-ab3c-d52691b4dbfc
webkitRequestPointerLock and webkitExitPointerLock limited to the same document of an active Pointer lock.
https://bugs.webkit.org/show_bug.cgi?id=91284

Reviewed by Adrienne Walker.

Previously, cross-talk between documents was possible, e.g. allowing one
document.webkitExitPointerLock to exit the lock from another document.
This change brings Pointer Lock closer to the Fullscreen API behavior,
and stops the pointer lock target from being transferable between
documents.

Source/WebCore:

Test: http/tests/pointer-lock/requestPointerLock-can-not-transfer-between-documents.html

* dom/Document.cpp:
(WebCore::Document::webkitExitPointerLock):
* page/PointerLockController.cpp:
(WebCore::PointerLockController::requestPointerLock):

LayoutTests:

* http/tests/pointer-lock/requestPointerLock-can-not-transfer-between-documents-expected.txt: Added.
* http/tests/pointer-lock/requestPointerLock-can-not-transfer-between-documents.html: Added.
* http/tests/resources/pointer-lock/iframe-common.js:
(document.onwebkitpointerlockchange):
(document.onwebkitpointerlockerror):
* pointer-lock/pointerlockchange-pointerlockerror-events-expected.txt:
* pointer-lock/pointerlockchange-pointerlockerror-events.html:


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@124301 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Layout Test media/video-currentTime-set.html is still flaky
https://bugs.webkit.org/show_bug.cgi?id=85003

Unreviewed gardening; test was fixed in r115462 but expectation was left behind.


* platform/chromium/TestExpectations:


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@124302 268f45cc-cd09-0410-ab3c-d52691b4dbfc