If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Bookmark retention option to further simplify the use of online books, manuals, and archives

RESOLVED EXPIRED

Status

()

Firefox
Bookmarks & History
--
enhancement
RESOLVED EXPIRED
13 years ago
11 years ago

People

(Reporter: Brian Scott Dobrovodsky, Assigned: Vladimir Vukicevic (BM, do not Cc or Request))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050228 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050228 Firefox/1.0.1

A bookmark option to retain the last visited url atop the bookmark url. A
bookmark of 'http://httpd.apache.org/docs-2.0/' would only retain a url which
contains the 'http://httpd.apache.org/docs-2.0/' base url. Leaving the base url
would deactivate the url retention of the particular bookmark and you would be
able to use the window/tab normally. More over, re-opening the bookmark would
send you to the last visited url.

Reproducible: Always

Comment 1

13 years ago
This is probably a bad idea. The items on the bookmark menu should be there
only because you the user have bookmarked them.

Last visited items can be found on the URL bar, the Go menu and the history
tab in the sidebar.
(Reporter)

Comment 2

13 years ago
(In reply to comment #1)
Perhaps an example would better illustrate this feature.

I want to learn python. So I go to python's website, bookmark it and enable
retention. After browsing through the site and reading a few chapters I close
firefox. The next day, I open the bookmark and it puts me on the chapter where I
left off, instead of taking me where the bookmark was originally created.

Comment 3

13 years ago
It is certainly possible to bookmark fragment identifiers.

Is what you asking for, a save state/save session feature? If so it
is a dup of one (or more) exisiting bugs.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → bookmarks
You need to log in before you can comment on or make changes to this bug.