Remove implementation of very legacy Mozilla-based Fullscreen API.
Blink has already removed support for the legacy Mozilla-based Fullscreen API by aliasing it to the W3C version. We should do the same.
Created attachment 296712 [details] Patch
<rdar://problem/29603053>
Created attachment 296723 [details] Patch for landing
Comment on attachment 296723 [details] Patch for landing Attachment 296723 [details] did not pass mac-debug-ews (mac): Output: http://webkit-queues.webkit.org/results/2683238 New failing tests: js/dom/dom-static-property-for-in-iteration.html
Created attachment 296746 [details] Archive of layout-test-results from ews115 for mac-yosemite The attached test failures were seen while running run-webkit-tests on the mac-debug-ews. Bot: ews115 Port: mac-yosemite Platform: Mac OS X 10.10.5
Comment on attachment 296723 [details] Patch for landing Attachment 296723 [details] did not pass mac-ews (mac): Output: http://webkit-queues.webkit.org/results/2683409 New failing tests: js/dom/dom-static-property-for-in-iteration.html
Created attachment 296747 [details] Archive of layout-test-results from ews100 for mac-yosemite The attached test failures were seen while running run-webkit-tests on the mac-ews. Bot: ews100 Port: mac-yosemite Platform: Mac OS X 10.10.5
Comment on attachment 296723 [details] Patch for landing Attachment 296723 [details] did not pass mac-wk2-ews (mac-wk2): Output: http://webkit-queues.webkit.org/results/2683699 New failing tests: js/dom/dom-static-property-for-in-iteration.html
Created attachment 296758 [details] Archive of layout-test-results from ews107 for mac-yosemite-wk2 The attached test failures were seen while running run-webkit-tests on the mac-wk2-ews. Bot: ews107 Port: mac-yosemite-wk2 Platform: Mac OS X 10.10.5
Created attachment 296938 [details] Patch for landing
Comment on attachment 296938 [details] Patch for landing Clearing flags on attachment: 296938 Committed r209730: <http://trac.webkit.org/changeset/209730>
Since Element.ALLOW_KEYBOARD_INPUT is gone now, will it make sense to remove fullscreen/full-screen-keyboard-enabled.html and get rid of bool parameter in supportsFullScreenForElement?
Oops, I've meant ChromeClient::supportsFullScreenForElement (and its callees where applicable)
(In reply to comment #14) > Oops, I've meant ChromeClient::supportsFullScreenForElement (and its callees > where applicable) Yes that seems reasonable.
Patch landed so I'm closing this bug. I guess the follow-up work (if any) can be done in separate bug.