Peter Bex wrote:
> When you set a margin on a float, and then by using some javascript
> you change any of the positioning properties ('top', 'left' etc), the
> double margin float bug disappears in IE6. In IE7, the margin is
> _subtracted_ from the position, instead! I assume this is because
> they implemented a 'quick hack': always subtract the margin from the
> position of a float, to counter the double margin effect.
Very interesting test-case.
If you fix IE6 'margin-doubling on floats' by adding 'display: inline'
to the float, then IE6 behaves like IE7 for that test-case. This
indicates that they've used a fix with the 'display: inline' effect
(whatever that is) in IE7, and not halved the margin as such.
> I think the combination of float:left and position: relative breaks
> the fix. This leads me to a final question: is it allowed to combine
> float+posrel? I can't find any mention of how this combination is
> supposed to behave in the spec.
Older Opera versions didn't support 'position: relative' on floats, but
Opera do now.
IMO: when the spec is unclear or doesn't say anything, then the
direction/solution a majority of the most compliant browsers agree on
can be seen as an indication of what will end up in a future version of
the spec. The spec becomes more practical and usable that way.
Have used 'position: relative' on 'floats' for years, and haven't
noticed any problems apart from lots of erratic jumping in IE/win if
'position: relative' is actually used to offset the float horizontally.
IE can't handle that and I've found it impossible in practical cases to
solve it. That hasn't changed at all for IE7.
regards
Georg
--
http://www.gunlaug.no
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
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/
