Comment #12 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
But, the more I think about it, the more it makes sense. Maybe the standard
is wrong
in this case (:O god forbid we come against the standard!). It's good that
we
question the standard sometimes in my opinion. So, which do you think it
should be:
1. Absolute positioned elements is offset with respect to its containing
block.
or
2. Absolute positioned elements is offset with respect to where it would
have been prior to being absolutely positioned. In other words, if left and
right is set to
auto (default value) then the elements left offset remains the same as it
were prior
to be absolutely positioned. The same goes for the elements top and bottom
properties.
I think that the second option is best for absolutely positioned elements.
Just see
how useful this could be by downloaded the test case with a extended
example.
But if the standards really require an absolutely position element to
offset, by
default, to its containing element, then why is it that placing a nbsp
before the
element allows it to be effected by text flow? Also margins effect it's
offset also.
It seems to me that the current implementation in webkit isn't really
making up it's
mind as to what to do with absolutely positioned element's default offset,
neither
Opera and IE8 for that matter.
Attachments:
absolutepositioninline.htm 1.4 KB
--
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
-~----------~----~----~----~------~----~------~--~---
