Personally I’m interested in your library, I’ve been looking at cross-browser script libraries to avoid needing to repeatedly compensate for browser differences, and I’ll be taking a look at you library soon.
DHTML pop-ups are what I’ve used in the past, but obviously that can cause many more problems.
Whoever said we should not try to control presentation is wrong. We can’t trust the browser or user to be able to interact with our pages in the most efficient or effective way. The only problem arises when ‘far from average’ users CAN’T access the content or function, as long as it is still POSSIBLE for EVERY user to use my web site then it is OK to add more usability for a subset of the users.
As ‘far-from-average’ users are in the minority, no user-focused designer would sacrifice good usability for the sake of a few.
Did God make the world flat so that everyone could got the same experience out of it? No.
Er anyway what was I saying? Oh yeah…
If pop-ups add value, then I will use pop-ups. If they can be implimented with no negative affect on ‘far-from-average’ users, then that’s how I want to impliment them.
So, good article!
I presume the use of having a DOCTYPE is so that computer programs and other non-human web browsers know what html/xml tags are being used and what attribues/values they can have.
The biggest problem with DOCTYPEs is that IE stops working in any predictable way. (IE’s quirks may be annoying but at least when it is in ‘quirks mode’ we can predict problems and take evasive action! Although I had hoped IE in strict mode would behave better and more predictably, I have not seen it do so yet).
Here’s an example of when using eXtensibility in documents is good…
meta-data is meta-data, it is information about information, why should we limit ourselves to the types/categories/headings of meta information that the W3C predicts to be a general range of good attributs for everyone?
Each web page is different, if you need to break the mould, then do so! (The W3C aren’t stupid, they made sure the functionality exists - custom DTDs).
In many cases I have HTML elements that have a peice of info specific to that element, where is the best place to put that info? answer - In an attribute of that tag!
It may not be standard but it’s useful for that element.
For example, if I want some abitary images in my page to change when the mouse hovers over them, I will write a generic script that swaps images, but because each image using that script needs to have its own individual hover-state image, I record the hover-image src in each individual IMG element:
Now in my behaviour layer I can make a script that swaps image “src=” with the “hover_src=” if/when it exists on the element.
Another example can be seen on my site:
Each form field has attributes providing specific information on how to validate its value.
I hope you agree these are good uses of HTML. In addition they do no harm.