Hello all,<br />
<br />
Does anyone know if it spaces in anchor tags cause problems in Netscape 4.x? This is my code:<br />
<br />
<a href='http://www.webdeveloper.com/forum/archive/index.php/#Component Technologies Group'>Component Technologies Group</a><br />
<br />
[more things here]<br />
<br />
<a name='#Component Technologies Group'>Welcome to the CTG</a><br />
<br />
When I click on the link in Netscape 4.x, nothing happens. I'm wondering if it's because I've used "Component Technologies Group" instead of, say "Component_Technologies_Group". <br />
<br />
Does anyone know anything about this? Dunk-a-scone.
<!--content-->It could be something like that - but bearing in mind that Netscape 4.x doesn't even like underscores in page element IDs, it's probably safest to have a name with both no spaces and no underscores. Probably.<!--content-->Only the anchor URL needs the # sign. The name does not.<br />
<br />
<a href=http://www.webdeveloper.com/forum/archive/index.php/"#Component Technologies Group">Component Technologies Group</a><br />
<br />
<a name="Component Technologies Group">Welcome to the CTG</a><!--content-->This was already alluded to by CyCo, but...<br />
Originally posted by manky <br />
<a href='http://www.webdeveloper.com/forum/archive/index.php/#Component Technologies Group'>Component Technologies Group</a>should be<br />
<br />
<a href='http://www.webdeveloper.com/forum/archive/index.php/##Component Technologies Group'>Component Technologies Group</a><br />
<br />
if your anchor has to have a "#" in it.<br />
<br />
Although CyCo's answer would be more correct.<!--content-->Basically there should be no blank spaces occurring within that name value.<!--content-->According to the W3C:ID and NAME tokens must begin with a letter ([A-Za-z]) and may be followed by any number of letters, digits ([0-9]), hyphens ("-"), underscores ("_"), colons (":"), and periods (".").So, as Robert says, Basically there should be no blank spaces occurring within that name value.<!--content-->I stand corrected.<!--content-->eep. i can't believe i made such a stupid mistake. i was so caught up with the spaces/no spaces thing that i didn't even notice that rogue # hanging about. thanks CyCo for pointing that out. (i guess i really made a HASH of things, snh snh)<br />
<br />
so here's the story: the anchors work in Netscape 4.x now, even though the spaces have been retained. thanks Geat (isn't life geat? sorry, kill me now), CyCo, gil davis and Robert Wellock for all your help.<!--content-->
<br />
Does anyone know if it spaces in anchor tags cause problems in Netscape 4.x? This is my code:<br />
<br />
<a href='http://www.webdeveloper.com/forum/archive/index.php/#Component Technologies Group'>Component Technologies Group</a><br />
<br />
[more things here]<br />
<br />
<a name='#Component Technologies Group'>Welcome to the CTG</a><br />
<br />
When I click on the link in Netscape 4.x, nothing happens. I'm wondering if it's because I've used "Component Technologies Group" instead of, say "Component_Technologies_Group". <br />
<br />
Does anyone know anything about this? Dunk-a-scone.
<!--content-->It could be something like that - but bearing in mind that Netscape 4.x doesn't even like underscores in page element IDs, it's probably safest to have a name with both no spaces and no underscores. Probably.<!--content-->Only the anchor URL needs the # sign. The name does not.<br /><br />
<a href=http://www.webdeveloper.com/forum/archive/index.php/"#Component Technologies Group">Component Technologies Group</a><br />
<br />
<a name="Component Technologies Group">Welcome to the CTG</a><!--content-->This was already alluded to by CyCo, but...<br />
Originally posted by manky <br />
<a href='http://www.webdeveloper.com/forum/archive/index.php/#Component Technologies Group'>Component Technologies Group</a>should be<br />
<br />
<a href='http://www.webdeveloper.com/forum/archive/index.php/##Component Technologies Group'>Component Technologies Group</a><br />
<br />
if your anchor has to have a "#" in it.<br />
<br />
Although CyCo's answer would be more correct.<!--content-->Basically there should be no blank spaces occurring within that name value.<!--content-->According to the W3C:ID and NAME tokens must begin with a letter ([A-Za-z]) and may be followed by any number of letters, digits ([0-9]), hyphens ("-"), underscores ("_"), colons (":"), and periods (".").So, as Robert says, Basically there should be no blank spaces occurring within that name value.<!--content-->I stand corrected.<!--content-->eep. i can't believe i made such a stupid mistake. i was so caught up with the spaces/no spaces thing that i didn't even notice that rogue # hanging about. thanks CyCo for pointing that out. (i guess i really made a HASH of things, snh snh
)<br /><br />
so here's the story: the anchors work in Netscape 4.x now, even though the spaces have been retained. thanks Geat (isn't life geat? sorry, kill me now), CyCo, gil davis and Robert Wellock for all your help.<!--content-->