Designer wrote:
I agree. The thing is, if top, middle and bottom are OK, surely left and
right are too? Where do you draw the line?
(my own view is that they probably are OK - like Patrick said,
pragmatism is the order of the day here, surely?)
I think so...
until we get a algorithm built into CSS and Browsers that says "place
this image in the container so that the text flows around it with the
least orphaned words" then we're going to have to make choices about
should it float left or right and whilst I think left and right are
*wrong* as class names I can't think of a way to differentiate classes
for image placement that make any long term maintainable sense.
the argument for semantic class names can be used to argue for left and
right in this case - e.g calling something p.red now means headaches for
maintenance in the future when p.red is now green, but creating
img.typea and img.typeb is just as much a nightmare if you forget which
type floats which way...
Pragmatism rules.
I want my CSS to be flexible, meaningful and written so I can read it
like a story (preferably without a translation guide...)
likewise the (x)html should make sense too, so when I look at the code
and the CSS in an editor I can picture what it *should* appear like.
;o)
--
Join me: http://wiki.workalone.co.uk/
Thank me: http://www.amazon.co.uk/gp/registry/1VK42TQL7VD2F
Engage me: http://www.boldfish.co.uk/portfolio/
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************