Re: [csswg-drafts] [css-page-floats] Absolutely positioned?

I took that to be the general point, but the details aren't clear:

There are several side effects of absolutely positioning things; I've 
listed several. It should be made clear which things about 
position:absolute apply, and which don't. Even with your reply, I 
don't know to what extent they are "like" absolutely positioned items.
 If they don't share all or most of the same features/side-effects, 
then an uninformed polfill will produce different results. 

I think the clearest and easiest way to deal with it is to go ahead 
and say that this property causes `position` to compute to `absolute`,
 overriding any other value of `position`on the element, causing it to
 ignore `top`, `right`, `bottom`, and `left` property values, and 
causing the `float-reference` to become the containing block 
(preventing other ancestors with non-static positions from becoming 
its containing block). 

Otherwise, if that's not the case, then you should detail how this is 
different from an absolutely positioned exclusion (aside from not 
needing any non-auto `top`, `right`, `bottom`, and `left` property 
values). And to what extent it is the same. Details should include 
auto margins, collapsing margins, auto widths, what happens when you 
page float an inline, what happens if you have `position:relative` and
 `top`, `right`, `bottom`, and `left` values on a page float, etc. 
(and probably other considerations). 

How can anyone create a polyfill without knowing these details, when 
absolute positioning changes these details? Some of these details can 
also add to your list of how inline floats are different from 
absolutely positioned exclusions. How page floats are different from 
absolutely positioned exclusions is an equally important thing to 
distinguish, after that list.

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

Received on Thursday, 30 June 2016 03:34:28 UTC