Remove glu's libtest rule from checker.py
https://bugs.webkit.org/show_bug.cgi?id=119674

Reviewed by Darin Adler.

* Scripts/webkitpy/style/checker.py: It is no longer used after r148032.


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@153954 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Define DOM_KEY_LOCATION_* constants on KeyboardEvent
https://bugs.webkit.org/show_bug.cgi?id=119341

Reviewed by Ryosuke Niwa.

Source/WebCore:

Add support for the DOM_KEY_LOCATION_* constants on KeyboardEvent as per
the specification:
http://www.w3.org/TR/DOM-Level-3-Events/#events-KeyboardEvent

Those constants are already supported by IE10, Firefox 22 and since
recently Blink.

Note that the following constants are not supported / exposed yet:
DOM_KEY_LOCATION_MOBILE and DOM_KEY_LOCATION_JOYSTICK.

Test: fast/events/keyboardevent-location-constants.html

* dom/KeyboardEvent.cpp:
(WebCore::keyLocationCode):
(WebCore::KeyboardEvent::KeyboardEvent):
* dom/KeyboardEvent.h:
* dom/KeyboardEvent.idl:

LayoutTests:

Make use of the new DOM_KEY_LOCATION_* constants in the KeyboardEvent
test cases instead of hardcoding their values.

* fast/events/constructors/keyboard-event-constructor-expected.txt:
* fast/events/constructors/keyboard-event-constructor.html:
* fast/events/js-keyboard-event-creation-expected.txt:
* fast/events/js-keyboard-event-creation.html:
* fast/events/keyboardevent-location-constants-expected.txt: Added.
* fast/events/keyboardevent-location-constants.html: Added.
* fast/events/keydown-leftright-keys-expected.txt:
* fast/events/keydown-leftright-keys.html:
* fast/events/keydown-numpad-keys-expected.txt:
* fast/events/script-tests/keydown-numpad-keys.js:
(testKeyEventWithLocation):
* platform/efl/fast/events/js-keyboard-event-creation-expected.txt:
* platform/gtk/fast/events/js-keyboard-event-creation-expected.txt:


git-svn-id: http://svn.webkit.org/repository/webkit/trunk@153955 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Remove didNewFirstVisuallyNonEmptyLayout from WebKit2
https://bugs.webkit.org/show_bug.cgi?id=119658

Reviewed by Darin Adler.

Source/WebKit2: 

Removing this function entirely will change some functionality in the Nightlies, 
but we think that is an acceptable difference for the Nightlies. If is does cause 
a problem though, we can roll out this patch and deprecate the function instead.

* UIProcess/API/C/WKPage.h:
* UIProcess/WebLoaderClient.cpp:
* UIProcess/WebLoaderClient.h:
* UIProcess/WebPageProxy.cpp:
(WebKit::WebPageProxy::initializeLoaderClient):
* UIProcess/WebPageProxy.h:
* UIProcess/WebPageProxy.messages.in:
* WebProcess/InjectedBundle/API/c/WKBundlePage.h:
* WebProcess/InjectedBundle/InjectedBundlePageLoaderClient.cpp:
* WebProcess/InjectedBundle/InjectedBundlePageLoaderClient.h:
* WebProcess/WebCoreSupport/WebFrameLoaderClient.cpp:
(WebKit::WebFrameLoaderClient::dispatchDidLayout):
* WebProcess/WebPage/WebPage.cpp:
(WebKit::WebPage::initializeInjectedBundleLoaderClient):

Tools: 

* MiniBrowser/mac/WK2BrowserWindowController.m:
(-[WK2BrowserWindowController awakeFromNib]):
* WebKitTestRunner/InjectedBundle/InjectedBundlePage.cpp:
(WTR::InjectedBundlePage::InjectedBundlePage):
* WebKitTestRunner/TestController.cpp:
(WTR::TestController::createWebViewWithOptions):



git-svn-id: http://svn.webkit.org/repository/webkit/trunk@153956 268f45cc-cd09-0410-ab3c-d52691b4dbfc
The LayoutMilestones didLayout callback should only fire for the main frame
https://bugs.webkit.org/show_bug.cgi?id=119457

Reviewed by Sam Weinig.

Source/WebCore: 

This patch makes it so that FrameLoader::didLayout(LayoutMilestones) is only ever 
called for the main frame. Technically this will change existing API for 
didFirstVisuallyNonEmptyLayoutInFrame and didFirstLayoutInFrame. Clients used to 
be able to register for those callbacks for any frame they wanted, however, now 
they will only ever get the callback when it applies to the main frame. We think 
that this is acceptable since we don’t know of any clients that ever used those 
APIs for a non-main frame. This change also makes nothing but sense for the 
didLayout(LayoutMilestones) callback, since that is a Page-level concept, so it 
should only fire for the main frame.

Only call didLayout for the main frame.
* dom/Document.cpp:
(WebCore::Document::setVisualUpdatesAllowed):

Assert that this is the main frame.
* loader/FrameLoader.cpp:
(WebCore::FrameLoader::didLayout):

Only call didLayout for the main frame.
* page/FrameView.cpp:
(WebCore::FrameView::performPostLayoutTasks):

Tools: 

Now that the didLayout callback only fires for the main frame, we want to make 
sure it will fire even when all of the content is in a subframe.

* TestWebKitAPI/TestWebKitAPI.xcodeproj/project.pbxproj:
* TestWebKitAPI/Tests/WebKit2/LayoutMilestonesWithAllContentInFrame.cpp: Added.
(TestWebKitAPI::didLayout):
(TestWebKitAPI::TEST):
* TestWebKitAPI/Tests/WebKit2/all-content-in-one-iframe.html: Added.



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