Improve representation of local named anchor URI's in Go menu history

NEW
Unassigned

Status

()

--
enhancement
17 years ago
9 years ago

People

(Reporter: bugmail, Unassigned)

Tracking

Trunk
Future
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

565 bytes, application/xml
Details
(Reporter)

Description

17 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:0.9.5) Gecko/20011015
BuildID:    2001101516

Accessing local named anchor links within a document results in multiple,
identical entries in the Go menu, all bearing merely the TITLE of the parent
document. More information can and should be provided the user in this context.

Reproducible: Always
Steps to Reproduce:
1. Access the attached test case
2. Click "Access paragraph 2.

Actual Results:  Two items reading "Local Named Anchor Test Case" appear in the
Go menu. This is the text from the TITLE element of the test case. No
information is shown or available to differentiate between the two.

Expected Results:  Some information should be given the user about these
identical menu items.

Some possible implementations include:

1. Tooltips on the menu items showing the anchor NAME or element ID attribute value
2. One Go menu item showing the document TITLE, with an heirarchical submenu
showing accessed named anchors
3. Document TITLEs in the Go menu, with anchor NAME or element ID attribute
values appended (e.g., "Local Named Anchor Test Case, Paragraph_2").

Note that it is up to content authors to apply meaningful NAME's and ID's to
anchors and other elements, just as it is up to them to apply meaningful TITLEs
to documents.
(Reporter)

Comment 1

17 years ago
Created attachment 55859 [details]
XHTML test case
(Reporter)

Comment 2

17 years ago
See also Bug 21521.
Status: NEW → ASSIGNED
Target Milestone: --- → Future

Updated

10 years ago
Component: History: Session → Document Navigation
QA Contact: claudius → docshell
Assignee: radha → nobody
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.