Position all elements relative by default#161
Conversation
At first I didn't think this belonged in normalize.css until I read point 4 of the normalize.css readme (Improves usability with subtle improvements), I believe this commit achieves that, as more of than not when we position an element absolutely we want to position it relative to its container, and not to the page itself. It's more economical with our time to position the container static if we should need to position this element to the page rather than its parent.
|
Well, I think you misunderstood the point. The usability improvements are intended for the user, not for the developer. Also, this isn't normal browser behavior nor is it a subtle "improvement". |
|
This would have major, breaking implications for trying to develop a website with this code included by default. You don't want to blindly change the |
|
What are the major, breaking implications of this addition? AFAIK position relative without a position specified is the same as static, is it not? |
|
Any absolutely positioned child element will be positioned relative to its nearest position-relative ancestor, so it's very different from |
|
Right. I guess that was kind of the point. |
At first I didn't think this belonged in normalize.css until I read
point 4 of the normalize.css readme (Improves usability with subtle
improvements), I believe this commit achieves that, as more of than not
when we position an element absolutely we want to position it relative
to its container, and not to the page itself. It's more economical with
our time to position the container static if we should need to position
this element to the page rather than its parent.