- From: R.S.V. <rsv@retemail.es>
- Date: Wed, 21 Jan 2004 21:19:00 +0100
- To: "Chris Lewis" <LewisCM@Cardiff.ac.uk>, <w3c-wai-ig@w3.org>, <jon@hackcraft.net>, <P.H.Lauke@salford.ac.uk>, <charles@sidar.org>, <jon@bunnyfoot.com>
Anchors and Bobby, Summary Thank you to Chris, P. H. Lauke, Jon Hanna, Jon Dodd and Charles McCathieNevile [Chris] - ignore Bobby's warning in this case [Ricardo] In my opinion, the best solution. [Chris] - change the wording of the headings or the links in the list at the top of the page (not recommended) [Ricardo] It doesn't work. See: http://www.timon.com/bobby3.html [Chris] - use id only to identify the anchors (and lose backwards compatibility) [Ricardo] I don't want to lose backwards compatibility. [Chris] - use an empty anchor (ie <a name="uno"></a>) before each heading [Ricardo] It doesn´t work. See: http://www.timon.com/bobby4.html [Jon Hanna] Why are you using name? Backwards compatibility? [Ricardo] Yes. In Netscape 4.7, relative links doesn't work if anchor is "id". [Jon Hanna] BTW. There is no need to use the <a> element when you are using id, you can put the id onto any element in the content. [Ricardo] Bobby doesn't report errors with "id" in elements, but we have the same problem with backwards compatibility. See: http://www.timon.com/bobby5.html [P. H. Lauke] "our boss still surfs the interweb powered by Netscrape 4.72" [Ricardo] Some people use browser that doesn't work with "id". [Charles] it looks like Bobby has a badly defined test here - i.e. a bug. I don't understand what it is picking up, but I don't see any reasonable argument that the error exists. [Ricardo] I agree with you. I think that is a bug. I'll send a bug report to Bobby. [Jon Dodd] Who cares if bobby flags a thing that is stupid? [Ricardo] Anyone who think that a bug in Bobby is relevant to accessibility lists. Maybe, some people in accessibility lists use Bobby and this information is useful for them. Thank you all. Regards, Ricardo Sánchez
Received on Wednesday, 21 January 2004 15:18:45 UTC