Comment #11 on issue 25612 by figaro1111: WebKit render bug: Absolutely positioned inline elements within a container that horizontally centers http://code.google.com/p/chromium/issues/detail?id=25612
karen said "ok here's what I found in the standards: http://www.w3.org/TR/CSS2/visuren.html#absolute-positioning which I interpret to mean absolute positioning overrides everything else." So does this mean that this isn't a bug, but rather the way the standards intend it to be? I don't know why this would ever be useful? It definitely seems buggy. How would I report a bug in the standards? This is what the spec says: "In the absolute positioning model, a box is explicitly offset with respect to its containing block. It is removed from the normal flow entirely (it has no impact on later siblings). An absolutely positioned box establishes a new containing block for normal flow children and absolutely (but not fixed) positioned descendants. However, the contents of an absolutely positioned element do not flow around any other boxes. They may obscure the contents of another box (or be obscured themselves), depending on the stack levels of the overlapping boxes." It says "It is removed from the normal flow entirely (it has no impact on later siblings)." I think that statement is trying to say what's in the parenthesis more than anything. I think what the spec should also have said was "It's default (starting) position is where it would have been if it where not absolutely position." It makes no sense to me why an element, if given absolute positioning should suddenly move the the left of it's containing element. It would make more sense if the element suddenly popped out of the text flow from where it was. But maybe my thinking is off, because in the spec it reads "In the absolute positioning model, a box is explicitly offset with respect to its containing block." I've updated the test case with a javascript example. Attachments: absolutepositioninline.htm 894 bytes -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
