Re: [fullscreen-tests] Test the many ways for fullscreen requests and exits to compete (#4250)

I suggest we stop spending too much time on behavior of calling `requestFullscreen` and `exitFullscreen` continuously. We can make spec and impls agree on what behavior should it be when calling multiple `requestFullscreen`s or multiple `exitFullscreen`s continuously, but mixing `requestFullscreen` and `exitFullscreen` isn't something sensible to do for web developers, and websites depending on that tends to be broken enough that I don't think it's worth worrying about the interoperability.

So again I suggest that we make those edge cases explicitly undefined. If we do see any real example that any website is broken somehow because of this in the future, we can revisit it then, but before that, I don't see much value digging too much here.

Given above, I suggest you remove the following tests:
* document-exit-fullscreen-vs-request-manual.html
* element-request-fullscreen-vs-exit-manual.html

Other tests look fine to me.

View on GitHub: https://github.com/w3c/web-platform-tests/pull/4250#issuecomment-266903047

Received on Wednesday, 14 December 2016 00:12:40 UTC