>I'd say you should get a clue in designing websites before you
>complain about lacklustre browser support (joke! ;)
WE should get a clue? Read this from www.w3.org the people who defined the
standards...
Guidelines for authoring
Here are some rough guidelines for HTML authors. If you use these, you are
more likely to end up with pages that are easy to maintain, look acceptable
to users regardless of the browser they are using, and can be accessed by
the many Web users with disabilities. Meanwhile W3C have produced some more
formal guidelines for authors. Have a look at the detailed Web Content
Accessibility Guidelines <http://www.w3.org/WAI/GL>.
A question of style sheets. For most people the look of a document - the
color, the font, the margins - are as important as the textual content of
the document itself. But make no mistake! HTML is not designed to be used to
control these aspects of document layout. What you should do is to use HTML
to mark up headings, paragraphs, lists, hypertext links, and other
structural parts of your document, and then add a style sheet to specify
layout separately, just as you might do in a conventional Desk Top
Publishing Package. That way, not only is there a better chance of all
browsers displaying your document properly, but also, if you want to change
such things as the font or color, it's really simple to do so. See the Touch
of style <http://www.w3.org/MarkUp/Guide/Style>.
FONT tag considered harmful! Many filters from word-processing packages, and
also some HTML authoring tools, generate HTML code which is completely
contrary to the design goals of the language. What they do is to look at a
document almost purely from the point of view of layout, and then mimic that
layout in HTML by doing tricks with FONT, BR and (non-breaking
spaces). HTML documents are supposed to be structured around items such as
paragraphs, headings and lists. Yet some of these documents barely have a
paragraph tag in sight!
>I'd also say that it's painfully obvious to Olli and David that
>the things you mention aren't implemented. Have patience,
>guys. Now, if you have REAL bugs..
I know that, I just tried to make an example for them to use during testing.
I'd actually think that things like CSS and javascript are more important
generally than bugs like 'it sometimes crashes if I do this sequence...' or
'its using all my chipram...'
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
