Bill Norton wrote:
>
>So, no sense in any further discussion on this - you cannot float an abs
element, period.
Well, tell it to MS, then. What's happening with their absolute,
right-floated, non-offset element isn't exactly floating, but it's not
exactly according to specs either.
If the specs tell you that you cannot do a certain thing, then you
should not do that thing, IMHO. If you do that thing, the result may be
unpredictable, especially in a faulty browser such as IE. If you do that
thing anyway, then the browser should ignore it. Fx does so in this case
and IE does not, but proceeds to do something unpredictable (unspecified
in the specs). You give some value to IE's action here?
Gus, you obviously place a lot more weight on specs than I do. Ultimately I
have to write to the browsers, not to the specs, and the main browser I have
to write to is IE. That's the unfortunate reality for me.
Due to the fact that some browsers had some difficulty in following some
of the specs, the web had some problems when author's wrote to the
quirks (behaviors) of some browsers. This is not the way it should be
done today. Authoring should be according to the specs with compensation
to accomodate any defective browser such as IE6. Generally it can be
done within the spec guidelines. This also means that one should check
with Fx/Opera _first_ and IE _last_. If IE is the odd-man out, IE will
be wrong 99% of the time.
>Regarding your, 'Do Offsets Matter for Static?' you should also be aware
that Static does not take any offsetting properties whether block or
inline.
Well, there's nothing that keeps you from specifying offsets for a static,
it's just that they will be ignored. This isn't like passing parameters to a
function where an invalid or meaningless parameter could make it crash.
Very much related to my first paragraph:
If the specs tell you that you cannot do a certain thing, then you
should not do that thing, IMHO. If you do that thing anyway, the result
may be unpredictable, especially in a faulty browser such as IE. In this
case it seems that Fx and IE both ignore (don't take) the offsets for
Static. So why would you then include it?
But it's true that statics don't "take" offsets because then, well, they'd
be relatives, wouldn't they?
Right. Which should tell you to not include offsets for Static.
--
Gus