In the current spec, when the content request fullscreen on the current fullscreen element, the call would be accepted, and a fullscreenchange event is fired without actually changing anything. It doesn't seem to make much sense to me.
fullscreenchange, as its name, should indicate that something is just changed. If nothing changes, we should fire fullscreenerror instead.
In the current spec, when the content request fullscreen on the current fullscreen element, the call would be accepted, and a
fullscreenchangeevent is fired without actually changing anything. It doesn't seem to make much sense to me.fullscreenchange, as its name, should indicate that something is just changed. If nothing changes, we should firefullscreenerrorinstead.