Andy Dingley <> wrote:
> So in HTML, you can't "precisely dictate the position of an image".
> This is by design, because it's not a good thing to be trying to do.
>
> With some features of HTML, then you can attempt to do this. The 1x1
> spacer gif was an early attempt.
Spacers need not be 1x1 ... you can make them any rectangular size. 1x1,
1x10, 50x100 ... whatever size you need.
It's a hack, true, but might be useful. For instance, if you wanted to
change the margin of a drop cap, put in a spacer gif. Need to change the
margin? Change the spacer. Yes, you could do soemthing better with CSS,
but the code fiddling is soemtimes more trouble than help. What's the
difference between two inline images instead of one? CSS is preferred for
some good reasons, but it is not your only option.
(A "Drop cap" is the large letter that starts a paragraph, like in a
magazine).
> Similar, but slightly less extreme, comments apply to
> the mis-use of tables for layout purposes.
Tables are fine for some layout - just not most layout. CSS is great for
layout, but not all layout. I have seen issues with both.
> If you use CSS to position an image 300 pixels from the left
> border, then this is _suggesting_ a position to be used.
A 300 pixel inline image will make the "suggestion" more of a mandate. At
worst, content will get bumped down lower on the page, or you might see
some scrollbars.
> One of the most important questions in web design at the moment is
> "How should your page degrade if a particular feature is unavailable?"
Golden. I totally agree with this.
> Good CSS-based and device independent design will work on a mobile
> phone _now_, without needing to re-work the pages.
It's when you screw up the CSS that things really go wonky. Some of the
W3C pages, for example, use CSS to their detriment.
The Doormouse
--
The Doormouse cannot be reached by e-mail without her permission.