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

Both usages do not seem to be very widespread. I didn't find any tutorial shows them, but I do see there is some code does this. Given that it only throws with strict mode, it's probably not a big issue. It would be great if we have data about how widespread those usages are, combined with strict mode.

I'm not familiar with how DOM APIs normally handle this kind of issues, but it seems to me that, if we want to be conservative, making the setters do nothing sounds like a reasonable compromise. But personally, I hope we could simply keep them readonly.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fullscreen/issues/2#issuecomment-99810880