Open Bug 216173 Opened 21 years ago Updated 12 years ago

Contextual menu item to create bookmark or copy link to any HTML element with id or name attribute

Categories

(SeaMonkey :: Bookmarks & History, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

People

(Reporter: joeclark, Unassigned)

References

()

Details

(Whiteboard: [2012 Fall Equinox])

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624

(X)HTML fragment identifiers, id and name, allow authors to provide anchors to
essentially any element in a document (absolutely any element in XHTML). If you
know the value of the attribute, you can link directly to that fragment of the
page by adding # and the value to the end of the URL.

But this requires you to search the source code, or the author must set up an
actual hyperlink up front.

For XHTML documents with many id attributes, as are typically made by authors
interested in standards compliance, it's a burden to make all those links, it
disrupts reading flow, and it's unreasonable to expect real people to be able to
read source code, no matter how nicely formatted.

Mozilla should sense when the element clicked on has an id or name attribute.
Contextual menu options could appear in those cases to (a) copy a link to that
fragment (the entire URL plus the identifier) *and* (b) bookmark the element.

Separately, id or name should show up in element properties.

The example to use is my book site and chapters (link given in other field
above), all of whose elements have an id. An extreme example, but many
standards-compliant authors include id or name. They're useful in CSS, for
example, among other reasons.



Reproducible: Always

Steps to Reproduce:
1. Find a page with id or name attributes on all or some elements.
2. Find one of those elements.
3. Right- or Ctrl-click on it.
4. Attempt to copy a link to that element or bookmark it.
5. Fail in this attempt.

Actual Results:  
No link or bookmark.

Expected Results:  
Once upgraded, Mozilla should link and/or bookmark the element on user command.

Cf. <http://fawny.org/blog/2003/07/?bugzilla#id-h1>
I forgot another reference: Purple.

<http://www.eekim.com/software/purple/>
Could not find any dupes. RFE->Confirmed.

Joe: you could make this yourself, as an extension, and post it to
<http://www.mozdev.org> as a top-level project, or to
<http://extensionroom.mozdev.org>
Status: UNCONFIRMED → NEW
Ever confirmed: true
Yeah, I could make it myself if I were a programmer. Wouldn't that be your
response to *any* feature request you didn't personally like?
Reporter: it was never my intention to sound like I was in disfavor of this
request. I merely suggested that you could, if you wanted to, make it yourself.
And I pointed you to some websites that carry great examples of Mozilla extensions.

Also, the fact that I added myself to the CC list suggests that this is a
feature that I would like to see as well.
A File Bookmark option would also be useful.
Product: Browser → Seamonkey
Reassigning as per Bug #32644
Assignee: p_ch → nobody
Checked on both Comment 0 and Comment 1 links, all anchors allow to add bookmark on them, so closing as WFM
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/18.0 Firefox/18.0 SeaMonkey/2.15a1
Build identifier: 20120921003032
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [2012 Fall Equinox]
(In reply to Phoenix from comment #7)
> Checked on both Comment 0 and Comment 1 links, all anchors allow to add
> bookmark on them, so closing as WFM

How?

I don't see any menu items for that in
Nightly 20120921 Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/18.0 Firefox/18.0 SeaMonkey/2.15a1.

The request is not about anchors which already have an “<a href=…”, but about those which do not.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Ok, your correction help me find where I make mistake while checking, request still valid, while I'm not sure that this right section for it...
Status: REOPENED → NEW
You need to log in before you can comment on or make changes to this bug.