show bookmark name as document/window title

RESOLVED EXPIRED

Status

SeaMonkey
Bookmarks & History
--
enhancement
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: Adam Hauner, Unassigned)

Tracking

({helpwanted})

Trunk
Future
helpwanted

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: WONTFIX? A lot of effort for not much gain?)

(Reporter)

Description

16 years ago
Bookmarks should support opening bookmark with it's name as document title,
forcing original document title or putting it to (). Why?

Bug 117045 was marked as WONTFIX by Hixie with resolution 'use bookmarklets'. I
think, that common user isn't familiar with creating javascript bookmarks
(futhermore in very small bookmark's location input box). IMHO will be this
feature very usefull for operations with bookmark groups - for example, my set
of Bugzilla queries has seven times in title 'BugList', what isn't perfect for
quick navigation. 

There should be checkbox in bookmarks' Info tab:
Name:          [                             ]
               [ ] Use name as document title 
Location:      [                             ]

Updated

16 years ago
Summary: [RFE] open bookmark with it's name in title → [RFE] show bookmark name as document/window title
Sounds like moderate feature creep to me, but at least the UI for this is pretty
well contained (we just need one checkbox in the bookmark properties window).

CONFIRMED.

I'm not sure how this would be implemented, though. Wait for page load and
change the title? Override the title so that even after following pages it
changes? How about changes occuring because of dynamic changes to the DOM
<title> element or the window.title property?

I'm thinking the best way to implement this would be to wait for the HEADLoaded
event (doesn't exist yet) and change the <title> element directly. But that
might not be a good idea.

Specifically, the example you gave (the bug list) is a very tough cookie. It
actually consists of two pages, first the "please stand by" page and then the
bug list. There are two <title> elements -- heck there are two entire documents.
How do you propose to handle that case?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: helpwanted
Whiteboard: WONTFIX? A lot of effort for not much gain?
Target Milestone: --- → Future
(Reporter)

Comment 2

16 years ago
I'm not skilled in DOM, so I could ask, if window.title should be switched to
read-only after setting title from bookmark's name? If this could be possible,
there isn't problem with second title in multipart HTML. 

BTW IMHO this bug need similar backend as bug 135944 (Preference to disable
changes of windows' title).
Setting it to read only would mean that _whatever_ page you then navigated to,
e.g. if you clicked on one of the bug links in the list, the title would remain
the same. That's not really an option.

(Actually that's not quite true; technically setting window.title to read only
would stop it for that page alone. However, since the bug list is two pages, it
wouldn't help you in that case and therefore I am assuming you meant to say
"block it at the tab level".)
(Reporter)

Updated

15 years ago
Summary: [RFE] show bookmark name as document/window title → show bookmark name as document/window title
Product: Browser → Seamonkey
Assignee: bugs → nobody
QA Contact: claudius → bookmarks

Comment 4

9 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 5

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.