4css aka deb wrote:
I had a layout that worked with IE6 really great, however, I used
the alsett clearing method, which I am finding isn't one that works
in IE7?
The method works...
http://www.tanfa.co.uk/archives/show.asp?var=300
...it is only a question about how one applies it.
Understanding has layout is the main one. I have read so much about
it, but for some reason it isn't clicking in.
The series of triggers for Layout in IE is non-standard...
http://www.satzansatz.de/cssd/onhavinglayout.html
...but the effect is (for the most part) pretty similar to what we
expect from more standard compliant browsers when we introduce block
formatting...
http://www.w3.org/TR/CSS21/visuren.html#block-formatting
Both Layout and block formatting establish a box with a calculated
area which contains all in-flow content/elements and isolates all
content/elements from what's outside this box's area.
- Note that floats are in-flow elements, as they are interacting with
all other in-flow elements. Thus Layout and block formatting
contain floats.
- Absolute and fixed positioned elements are take out of the flow - they
do not interact with in-flow elements. Thus Layout and block
formatting do not contain these positioned elements.
- IE7 and older complicates positioning a bit since they can only
absolute position an element out of a box/container if that
box/container has Layout.
- Layout in itself is a bug the people behind IE made extensive use of
to counteract other bugs in the Trident engine - a quick but problematic
way to fix things. They are taking a somewhat more sound approach for
IE8 - fixing and/or avoiding the actual bugs, so we can rely more on
what's written in the standards when IE8 final arrives.
Over flow hidden used for clearing?
Not for clearing, but for block formatting. See above.
Also the use of zoom?
In this context IE's proprietary zoom is just another trigger for
Layout - a hasLayout trigger if you like.
See Thoughts on IE hack management...
http://onhavinglayout.fwpf-webdesign.de/hack_management/
Zoom does of course have its own effects beyond that, as do all
Layout and block formatting triggers.
You must keep this basic vs. additional effects in mind when choosing
clearing and containment methods, or else you may run out of options and
not know how to solve design problems.
Forgive my questions, but as I stated it has been a while for me and
I feel like I have lost a lot of what I had within my brain over the
past year plus.
You may as well take advantage of that loss, and clear out any other
misconceptions you may have collected over the years. Both standards and
browsers' implementation of them have changed over the years, and old
concepts tend to become less accurate and in many cases misleading over
time because of this. It's a natural/logical process.
A bit OT, but I tend to perform clear, update, refine concepts
processes on my brain at irregular intervals - quite often really, to
avoid being hampered by old information, observations and potential
misconceptions. In a field as unfinished/unstable as web design, such
frequent personal unlearn, relearn, refine processes are necessary if
one wants to keep phase with progress and keep track of regress.
Old browsers (and their bugs) never die, they just fade away -
unfortunately :-)
regards
Georg
--
http://www.gunlaug.no
__
css-discuss [cs...@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
