183751 - nbc4.com - Non-standard name (id) prevents href from working , <a name="#A"> vice <a name="A">

Status: RESOLVED FIXED

(Tech Evangelism Graveyard :: English US, defect)

Description

[Scott Kitterman]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021204
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021204

The page in question has a list of weather related closings and an alphabetic
index.  Clicking on the letters in the index results in the url displayed as the
current position changing, but the window doesn't actually go to the anchor.

Reproducible: Always

Steps to Reproduce:
1. Go to url.
2. Click on one of the letters in the index
3. 

Actual Results:  
The displayed url changes, but you don't go to the right place on the list.

Expected Results:  
Go to the right place on the list.

I don't know how long that page will be up, so I've created a reduced test case
from the page that demonstrates the problem.

Also, changing the <a name="#A">A</a> tag to id= (which is preferred in HTML
4.0) doesn't change the result.

Also saw the same problem with Mozilla 1.2.1 with WIN98SE and with Mozilla 1.1
and WIN2K SP3.

Comment 1

[Scott Kitterman]

Attachment: Test case for the problem

Test case mentioned above.

Comment 2

[Michael Lefevre]

neither your testcase or the page is correctly coded. href="#A" refers to an
element called "A", not an element called "#A". if you remove the # from the
name or id attribute, it works fine.

Internet explorer automatically corrects the error - it will ignore any extra #s
- which encourages people to get it wrong :(

maybe this should be an evangelism bug for the nbc4 site?

Comment 3

[Scott Kitterman]

Yes.  I agree.  It ends up being more than just NBC4.com as it appears that
content is provided by ibsys.com, which appears to serve content to a LOT of
local TV station web sites.

Comment 4

[Michael Lefevre]

if you'd like to help out, you could always email the webmaster of the nbc site
(or the content providing site if it's their code) yourself, rather than waiting
for the overworked tech evang team to get around to it... thanks

Comment 5

[Scott Kitterman]

E-mailed [e-mail].  It was the only e-mail address I could find.  I don't
know what the odds are of the e-mail actually getting to someone who might do
something about it.  We'll see.

Comment 6

[Scott Kitterman]

Status update - I checked the site again and the problem still exists.  I never
heard back from the e-mail I sent last month.  

Comment 7

[Susie Wyshak]

-->doron

Comment 8

[Scott Kitterman]

WFM now.  Looks like they've updated their site.  closing.