If validation is used as a tool for making sure the page structure
itself is sound (as opposed to following the standards for their own
sake), it can help-- some things you want to have just aren’t covered
by the standards, or don’t work because browsers don’t implement them
So a mixture of having pages validate (and tools aware of XHTML
working nicely) and “injecting” workarounds for both of the
aforementioned issues is working out fine. For me.
The “autocomplete” attribuet is probably a bad example anyway, as
normally you always want this the way the user decides, except for
certain cases (for example if you implement server-side
autocompleting, and browsers interfere).
Alas, I don’t think there’s one single unified answer for how to deal
with this, it really depends on the circumstances, your “style” of
Am 03.03.2007 um 15:00 schrieb Russell N.: