Re: [whatwg/fullscreen] Make fullscreenElement and fullscreenEnabled [Replaceable]? (#2)

Ah, `t.fullscreenElement = t.fullscreenElement || []` would throw an exception if `t.fullscreenElement` is null.

Using type `any` for these attributes is very low risk, but also very sad to see stuck forever. Maybe we could do it but add deprecation messages to the setter and measure usage, to see how far we are from usage where just sticking with the current spec would be acceptable from a compat perspective? I don't mind if the spec comes along for the ride as well, as long as we don't close the door on a sane spec before we have some usage data.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fullscreen/issues/2#issuecomment-215688819

Received on Friday, 29 April 2016 11:31:04 UTC