Re: [csswg-drafts] [css-position] Interoperability issues with absolute positioning (#3952)

Afaict from your description, Firefox's behavior is correct.

In the first case, adding an outside-positioned marker box should have no effect on the layout of the contents of a block, so switching between 'list-item' and 'block' should not affect the abspos position.

Wrt the second case, the static position is calculated from the "hypothetical position" of the box if its 'position' value had been 'static'. When you add 'display: block' to that, then that position changes because  if it were a block, it would move to the next line. You can see this by removing 'position: absolute'. The spec allows the UA to "make a guess" as to the probable location of the box, so technically Chrome and Safari are spec-compliant, but Firefox is more correct. Afaict.

The active spec for abspos, btw, is CSS2: css-position is not known to be reliable for anything other than 'position: sticky'. https://drafts.csswg.org/css2/visudet.html#abs-non-replaced-width

-- 
GitHub Notification of comment by fantasai
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3952#issuecomment-494887234 using your GitHub account

Received on Wednesday, 22 May 2019 18:43:30 UTC