Comment 1 by jteh on 2009-07-05 00:55
The reporting of same page links is a duplicate and was reported in #141. As I noted there, browser users in general cannot differentiate between same page and external page links unless the site marks them in some way, so I don't believe it is important to implement this. Please continue discussion on this part of the issue in #141.

I'm hijacking this ticket to cover the jumping to anchors issue. For me, if I press enter on a same page link in Firefox, it does correctly jump to the anchor. However, it often doesn't when you access the URL directly. I assume the latter is what you are referring to? Unfortunately, Firefox doesn't expose sufficient information for us to do this via accessibility APIs, so we'll need to discuss this with them.
Changes:
Changed title from "NVDA should report and jump to Html anchors accurately" to "When loading a URL with a target anchor, NVDA should jump to that anchor"

Comment 2 by jteh on 2011-03-01 22:24
This already works in IE (1fd7e13).

It still doesn't yet work in Firefox. We need MozillaBug:617544 to fix this.

Comment 3 by jteh on 2011-10-11 03:16
After MozillaBug:691734 (fixed in Gecko 10) and 4a95a5e, we will get this right as long as the document is loaded while NVDA is running. We still need MozillaBug:617544 to get this right for documents loaded before NVDA is started.

Comment 4 by kevinchao89 on 2011-10-11 10:16
Excellent! Thanks! Confirmed fixed: snapshot main-4720.

I think this is fixed everywhere it should have been, right?

Almost. As noted in #360 (comment):

We still need MozillaBug:617544 to get this right for documents loaded before NVDA is started.

I think that's a pretty low priority use case, though. Also, the Mozilla bug was closed due to inactivity.

I'm going to close this, since this works in the majority of real world cases.

In Google Chrome it is still jumping the external link anchor, do you have any adjustment forecast?