CSS position absolute and fullscreen API

NEW
Unassigned

Status

()

Core
Layout
5 years ago
5 years ago

People

(Reporter: hsablonniere, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
Hey,

CSS positions behaves differently when in fullscreen (using the new API) in webkit and gecko. I tweeted Anne VK and he seems to say that Gecko isn't doing the right thing.

I'm not sure of who's right on that point so I ask for more help here and maybe this will be fixed in FF or I'll have to post on webkit bugtracker. Here's a test case to explain my point. Test it in both rendering engines. Because you can't trigger fullscreen api on iframe that haven't the proper attribute I added the direct link for testing and the source link.

Test case direct link
http://jsfiddle.net/2uNzk/1/show/light/

Test case sources
http://jsfiddle.net/2uNzk/1

What do you think ?
Chris, could you take a look please?
Flags: needinfo?(cpearce)
It looks to me like this is a bug in Chrome's fullscreen implementation; Chrome isn't applying the width:100%;height:100%;position:fixed;top:0;right:0;bottom:0;left:0 styles to the element which is requesting fullscreen.

Chrome has never done this IIRC.

Anne: in comment 0 the reporter reports that you said Chrome's behaviour in the testcase in comment 0 was correct here, if that's so, can you outline why?
Flags: needinfo?(cpearce)
Flags: needinfo?(annevk)

Comment 3

5 years ago
Well he overrides position/top/width afaict and there's nothing in the specification that says we should not respect that.

(I'm also starting to think that given ::backdrop we should maybe have the :not(:fullscreen) styles only for certain replaced elements, such as video/iframe/object.)
Flags: needinfo?(annevk)
You need to log in before you can comment on or make changes to this bug.