- From: Philip Jägenstedt <web-platform-tests-notifications@w3.org>
- Date: Fri, 25 Nov 2016 14:03:10 GMT
- To: public-web-platform-tests-notifications@w3.org
I've also tested everything under http://w3c-test.org/submissions/4250/fullscreen/ in Edge 15.14959 and these added tests fail: * api/document-exit-fullscreen-twice-manual.html (wrong fullscreenElement) * api/document-exit-fullscreen-vs-request-manual.html (extra fullscreenchange event) * api/element-request-fullscreen-and-move-manual.html (wrong fullscreenElement) * api/element-request-fullscreen-and-move-to-iframe-manual.html (extra fullscreenchange event) * api/element-request-fullscreen-and-remove-manual.html (extra fullscreenchange event) * api/element-request-fullscreen-twice-manual.html (wrong fullscreenElement) * api/element-request-fullscreen-vs-exit-manual.html (wrong fullscreenElement) @aliams, it would be very helpful if you could look into these failures and protest if you think making them pass would be difficult in Edge. I think I can match Firefox to make them pass in Chrome, but will make sure before landing spec or test changes. These existsing/modified tests also fail, can you investigate? * api/document-exit-fullscreen-manual.html (event target is element, not document) * api/document-fullscreen-element-manual.html (modifying fullscreen element stack synchronously) * api/element-ready-check-fullscreen-iframe-child-manual.html (test is wrong) * api/element-ready-check-iframe-child-manual.html (test is wrong) * api/element-request-fullscreen-manual.html (wrong event target) * api/element-request-fullscreen-non-top-manual.html (wrong fullscreenElement) * api/element-request-fullscreen-not-allowed.html (wrong event target) View on GitHub: https://github.com/w3c/web-platform-tests/pull/4250#issuecomment-262962725
Received on Friday, 25 November 2016 14:03:22 UTC