Re: [WSG] there is no attribute name

2005-05-15 Thread Thierry Koblentz
Thomas Ditmars wrote: div id=content ... Does this also apply to HTML 4.01 Strict? I guess my actual question is: What is the proper way of coding '#anchor-name' links in HTML 4.01 Strict? It is best to use *both* (up to XHTML 1.0) *with* a A element, to be nice to old browsers. You may want

RE: [WSG] there is no attribute name

2005-05-15 Thread Geoff Pack
Michael Cordover wrote: Yup, same mechanism. The #anchor has *always* referred to an id in the spec, referring to a name as a bit of an extra feature (read: incompatibility included for fun). That's a bit arse backwards. 'Name' has been the target of #anchors ('fragment identifiers') since

[WSG] there is no attribute name

2005-05-14 Thread Chris Stratford
Hey List, 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... #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

Re: [WSG] there is no attribute name

2005-05-14 Thread Jan Brasna
Just a question - I am using a XHTML 1.1 Strict DTD. 1.1 doesn't diverse between strict and others. There is just one 1.1 spec. It seems that you cannot giveform elements or anchor elements a name this causes a few issues... Not exactly... #1 - anchors - when I have a SKIP TO CONTENT link. It

Re: [WSG] there is no attribute name

2005-05-14 Thread Patrick H. Lauke
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

Re: [WSG] there is no attribute name [SOLVED - THNX Jan Patrick]

2005-05-14 Thread Chris Stratford
Ahh thanks guys! Sorry I did make a few mistakes when typing that up :S Some of that I did know, but just mistyped when I sent it. Sorry :( but I definatly have been sent in the right direction :) Thanks guys! Appreciate it! - Chris Chris Stratford wrote: Hey List, Just a question - I am using a

Re: [WSG] there is no attribute name

2005-05-14 Thread Thierry Koblentz
Patrick H. Lauke wrote: The proper way in XHTML is using fragment identifiers: giving an ID to an element, and linking to that, e.g. a href=#contentgo to content/a div id=content I've found that using id instead of name for anchors (including a href attribute) creates an accessibility issue

Re: [WSG] there is no attribute name

2005-05-14 Thread Patrick H. Lauke
Thierry Koblentz wrote: I've found that using id instead of name for anchors (including a href attribute) creates an accessibility issue since some browsers (at least MSIE) find the location, but are unable to keep track of the link sequence re: tabbing navigation. I posted a message a while back

Re: [WSG] there is no attribute name

2005-05-14 Thread Thierry Koblentz
Patrick H. Lauke wrote: I found that, even when using NAME, IE (particularly IE6/SP2 on WinXP/SP2) can exhibit this same behaviour of forgetting the right tab order. In fact, I just created a super simple page where my IE (version and OS as above) just does that

Re: [WSG] there is no attribute name

2005-05-14 Thread Thomas Ditmars
On 14-May-05 13:47, Patrick H. Lauke wrote: Chris Stratford wrote: #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:

Re: [WSG] there is no attribute name

2005-05-14 Thread Michael Cordover
Hi Thomas, On 5/15/05, Thomas Ditmars [EMAIL PROTECTED] wrote: On 14-May-05 13:47, Patrick H. Lauke wrote: a href=#contentgo to content/a ... div id=content ... Does this also apply to HTML 4.01 Strict? I guess my actual question is: What is the proper way of coding '#anchor-name' links