Changeset 87022 in webkit
- Timestamp:
- May 21, 2011 3:30:01 PM (13 years ago)
- Location:
- trunk
- Files:
-
- 6 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/LayoutTests/ChangeLog
r87021 r87022 1 2011-05-21 Jeremy Noble <jer.noble@apple.com> 2 3 Reviewed by Eric Carlson. 4 5 WebKit2: fix failing fullscreen/full-screen-remove* tests. 6 https://bugs.webkit.org/show_bug.cgi?id=61027 7 8 * platform/mac-wk2/Skipped: Unskip most fullscreen/ tests. 9 1 10 2011-05-21 Justin Schuh <jschuh@chromium.org> 2 11 -
trunk/LayoutTests/platform/mac-wk2/Skipped
r86981 r87022 359 359 fast/text/offsetForPosition-complex-fallback.html 360 360 fast/text/reset-drag-on-mouse-down.html 361 fullscreen/full-screen-cancel.html362 361 http/tests/local/blob/send-hybrid-blob.html 363 362 http/tests/local/drag-over-remote-content.html … … 1660 1659 inspector/console/console-long-eval-crash.html 1661 1660 1662 # WebKit2 needs fullscreen support 1663 # https://bugs.webkit.org/show_bug.cgi?id=56318 1664 fullscreen/ 1661 # WebKit2 needs fake key event support 1662 fullscreen/full-screen-frameset.html 1663 fullscreen/full-screen-keyboard-disabled.html 1664 fullscreen/full-screen-keyboard-enabled.html 1665 1665 1666 1666 # WebKit2 needs to support synchronous creation of about:blank/data:url frames -
trunk/Source/WebCore/ChangeLog
r87020 r87022 1 2011-05-21 Jeremy Noble <jer.noble@apple.com> 2 3 Reviewed by Eric Carlson. 4 5 WebKit2: fix failing fullscreen/full-screen-remove* tests. 6 https://bugs.webkit.org/show_bug.cgi?id=61027 7 8 * dom/Document.cpp: 9 (WebCore::Document::fullScreenChangeDelayTimerFired): dispatchEvent can be 10 synchronous, so make sure to check whether the current element is 11 in the DOM before dispatching. 12 1 13 2011-05-21 Gavin Peters <gavinp@chromium.org> 2 14 -
trunk/Source/WebCore/dom/Document.cpp
r86976 r87022 4987 4987 if (!element) 4988 4988 element = documentElement(); 4989 4990 element->dispatchEvent(Event::create(eventNames().webkitfullscreenchangeEvent, true, false));4991 4989 4992 4990 // If the element was removed from our tree, also message the documentElement. 4993 4991 if (!contains(element.get())) 4994 4992 m_fullScreenChangeEventTargetQueue.append(documentElement()); 4993 4994 element->dispatchEvent(Event::create(eventNames().webkitfullscreenchangeEvent, true, false)); 4995 4995 } 4996 4996 } -
trunk/Source/WebKit2/ChangeLog
r87005 r87022 1 2011-05-21 Jeremy Noble <jer.noble@apple.com> 2 3 Reviewed by Eric Carlson. 4 5 WebKit2: fix failing fullscreen/full-screen-remove* tests. 6 https://bugs.webkit.org/show_bug.cgi?id=61027 7 8 * WebProcess/InjectedBundle/InjectedBundlePageFullScreenClient.cpp: 9 (WebKit::InjectedBundlePageFullScreenClient::exitFullScreenForElement): Call the 10 exit functions (was calling the enter functions). 11 1 12 2011-05-20 Jeremy Noble <jer.noble@apple.com> 2 13 -
trunk/Source/WebKit2/WebProcess/InjectedBundle/InjectedBundlePageFullScreenClient.cpp
r84206 r87022 62 62 void InjectedBundlePageFullScreenClient::exitFullScreenForElement(WebPage *page, WebCore::Element *element) 63 63 { 64 if (m_client.e nterFullScreenForElement) {64 if (m_client.exitFullScreenForElement) { 65 65 RefPtr<InjectedBundleNodeHandle> nodeHandle = InjectedBundleNodeHandle::getOrCreate(element); 66 m_client.e nterFullScreenForElement(toAPI(page), toAPI(nodeHandle.get()));66 m_client.exitFullScreenForElement(toAPI(page), toAPI(nodeHandle.get())); 67 67 } else 68 68 page->send(Messages::WebFullScreenManagerProxy::ExitFullScreen());
Note: See TracChangeset
for help on using the changeset viewer.