RE: [WSG] there is no attribute "name"
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 HTML 1.
Can you imagine how many links would have broken if it had been removed from
html 4?
Geoff.
**
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
**
Re: [WSG] there is no attribute "name"
Thomas Ditmars wrote: >> ... > 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 to remove styles, but not functionality ;-) This should take care of old browsers, tabbing navigation and the Validator. Thierry | http://www.TJKDesign.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 **
Re: [WSG] there is no attribute "name"
Hi Thomas, On 5/15/05, Thomas Ditmars <[EMAIL PROTECTED]> wrote: > On 14-May-05 13:47, Patrick H. Lauke wrote: > > go to 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?" Yup, same mechanism. The #anchor has *always* refered to an id in the spec, referring to a name as a bit of an "extra feature" (read: incompatibility included for fun). HTH, mjec -- http://mine.mjec.net/ ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help **
Re: [WSG] there is no attribute "name"
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 ... 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. > > go to 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?" -- __ Thomas Ditmarszarggg [at] zarggg [dot] net KeyID: 0x2FAAE151 http://zarggg.net/blog2/index.php -- ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help **
Re: [WSG] there is no attribute "name"
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 > http://dev.splintered.co.uk/IE_tab_order/. Hi Patrick, That's correct, NAME by itself is not bullet proof, but if you include a href attribute in the named anchor (as mentionned in my post) it "fixes" MSIE. Try: and you'll see that IE gets it right. > And, in a weird twist, there are situations where, even using ID / > fragment identifiers, IE gets it right (see for instance I've also seen cases where it works fine, but I still have no clue why ;-) FYI: I've also found out that styling an A element with no content (a "regular" anchor) using "position:absolute" makes MSIE ignore the "location" of this element, so IE does not jump to that anchor. Anyway, it is important for people implementing "skip nav" links to *check* them in IE to see if they work with keyboard navigation. Thierry | http://www.TJKDesign.com | CSS-P Templates compatible NN4.7 - | CSS Popups | CSS Tabs | CSS Dropdown Menus | Articles and Tutorials | ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help **
Re: [WSG] there is no attribute "name"
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 about this, warning people that "skipnav" links built this way are just *useless*. 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 http://dev.splintered.co.uk/IE_tab_order/. And, in a weird twist, there are situations where, even using ID / fragment identifiers, IE gets it right (see for instance www.salford.ac.uk, where the second tab puts you on a 1x1 pixel skip link (I know, not ideal in itself, but this was done about 1 1/2 years ago)...following that link in IE (even IE 5) puts the next tab correctly (on the "order a prospectus" link top right, skipping all of the navigation). So, seems more like a complex bug in IE which depends on some unfathomable factors, rather than a problem purely with using IDs. -- 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 **
Re: [WSG] there is no attribute "name"
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. > go to content > 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 about this, warning people that "skipnav" links built this way are just *useless*. HTH, Thierry | http://www.TJKDesign.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 **
Re: [WSG] there is no attribute "name" [SOLVED - THNX Jan & Patrick]
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 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 ... Isn't this the only *proper* way of anchoring inside the page??? #2 - forms - when I have custom buttons (javascript: document.formnamehere.submit()) That doesn't work. My problem is that form buttons don't look or act the same in all browsers, so I use a styled like a button. When they click it, it uses that javascript to submit the form. But it requires the form to have a name... Why is the NAME attribute ruled out nowfor those two elements? Doesn't that have a very limiting effect on the forms? I know can have a name - because it works with ... Any ideas? Sorry if this has been discussed over and over - just it has never come up with my work before?? Cheers - Chris ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ** ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help **
Re: [WSG] there is no attribute "name"
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 ... 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. go to 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 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 can have a name - because it works with ... 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 **
Re: [WSG] there is no attribute "name"
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 doesn't like the NAME I have given the ... Isn't this the only *proper* way of anchoring inside the page??? No. #anchor-name skips also to #2 - forms - when I have custom buttons (javascript: document.formnamehere.submit()) That doesn't work. Sure. Because you should use DOM and again - it's sticked to ID (see getElementById() ...) My problem is that form buttons don't look or act the same in all browsers, so I use a styled like a button. Not a good idea... (JS off, semantics, usability...) I know can have a name - because it works with ... Eh, label binding shlould be again on ID... The name="" attrib on inputs it for the parametrizing / query. It's still send in the form of "action.url?name1=value1&name2=value2" etc. Sorry if this has been discussed over and over No problem, I just hope I'll show you the right way ;) -- Jan Brasna aka JohnyB :: www.alphanumeric.cz | www.janbrasna.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 **
[WSG] there is no attribute "name"
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 ... Isn't this the only *proper* way of anchoring inside the page??? #2 - forms - when I have custom buttons (javascript: document.formnamehere.submit()) That doesn't work. My problem is that form buttons don't look or act the same in all browsers, so I use a styled like a button. When they click it, it uses that javascript to submit the form. But it requires the form to have a name... Why is the NAME attribute ruled out nowfor those two elements? Doesn't that have a very limiting effect on the forms? I know can have a name - because it works with ... Any ideas? Sorry if this has been discussed over and over - just it has never come up with my work before?? Cheers - Chris ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help **
