Xidorn Quan
Xidorn Quan
Oh... I indeed didn't pay much attention on this side. What Gecko currently does is that, we have an internal (non-web-exposed) CSS property `-moz-top-layer`, which we apply value `top` for...
The current spec says the dimensions are changed in parallel to the next animation frame, right? It may not that easy to change dimensions in animation frame, as changing window...
In addition, the dimensions of viewport (from Window.{outer,inner}{Width,Height}) is updated synchronously when the size gets changed. Inconsistency between the document state and those properties might also be a problem.
The size is changed at some moment which we probably cannot fully control, but we can do stuff when that happen. That's the point. When a document is in a...
The change is... well, yes, but the timing is unpredictable. e.g. something like ``` text request fullscreen window size change finishes v v |--------------------|--------------------|--------------------| ^ ^ ^ ^ vsync vsync...
First of all, there is a way to get all fullscreen elements, and there is a way to check whether a specific element is in fullscreen state. That way is...
> `querySelectorAll` ... usage is common enough, we can certainly optimize it from the UA side (based on top layer stack that UAs are aware of) Think about it twice,...
The output on Firefox is: ``` 0 The VENDOR-specific :fullscreen Pseudo Class is :fullscreen fullscreenchange.html:35:3 ----------------------------------- fullscreenchange.html:37:3 5.236 DOCUMENT fullscreenchange: There is at least one element in fullscreen mode. The...
> Assuming CSS selectors (when fixed/implemented) then offer a mechanism to have knowledge of multiple fullscreen elements, could their ORDER be determined? `querySelectorAll` is guaranteed to return elements in the...
No. Fullscreen mode is not a web-exposed feature, and website is not supposed to be aware of that. Website should just get a resize event for the viewport size change....