Chris Stratford wrote:
Just a question - I am using a XHTML 1.1 Strict DTD.
It seems that you cannot giveform elements or anchor elements a "name" this causes a few issues...
Form elements, of course you can. Anchors, no.
#1 - anchors - when I have a SKIP TO CONTENT link. It doesn't like the NAME I have given the <a>... Isn't this the only *proper* way of anchoring inside the page???
The proper way in XHTML is using fragment identifiers: giving an ID to an element, and linking to that, e.g.
<a href="#content">go to content</a>
...
<div id="content"> ...
#2 - forms - when I have custom buttons (javascript: document.formnamehere.submit())
Use proper DOM javascript,
My problem is that form buttons don't look or act the same in all browsers,
How exactly? What are you trying to achieve? I find that styling submit buttons via CSS works pretty well across all modern browsers.
so I use a <a> styled like a button. When they click it, it uses that javascript to submit the form.
This creates accessibility problems for anybody with javascript unavailable or disabled, and is generally a bad idea.
I know <input> can have a name - because it works with <label>...
the FOR attribute in labels refers to a form element's ID, *not* its name!
-- Patrick H. Lauke _____________________________________________________ re�dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com
****************************************************** The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
