Xidorn Quan

Blink do A for ``. For fullscreen, I believe all browsers currently still use `:root:fullscreen-ancestor { overflow: hidden; }`, which is the third way I mentioned. However, we have removed...

If we can do B directly, we don't need to override `overflow`. If we decide that we do want A, then we do need to find a way to suppress...

> I'm starting to think that even for fullscreen content you might want to be able to scroll, with the option to override that from CSS if the developer feels...

In fullscreen, all ancestors up to the root of the document should already have been hidden behind `::backdrop` by default, so it doesn't make sense to hide their scrollbars. The...

Let me check how did I resolve this... I definitely met this issue before, otherwise I wouldn't file this issue :)

So what I did is, explicitly overriding the viewport's scrollbar style (without touching anything else) when the fullscreen element is neither null nor the root. (Code and comment can be...

The root element is explicitly excluded so that people can request fullscreen on the root and have the whole document be viewed in fullscreen as if in normal window.

Based on CSS spec, the viewport does have some kind of style, and viewport is not the root element in the DOM tree. You can find the following paragraph in...

> Is the viewport something that has style at all, or could this be the root element? If it's the root element, should this override show up in the computed...

It returns `false` for background window, but `true` for background tab. It seems in Chrome, background tab wouldn't be allowed to enter fullscreen either, how does that work? We stop...