Bookmarks duplicate on importation from master Bookmark HTML file.



16 years ago
13 years ago


(Reporter: arphaxed, Assigned: p_ch)



Firefox Tracking Flags

(Not tracked)




16 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312

I choose to have uniform bookmarks for ALL users.  I keep a template (or Master
file) in a directory.  Upon importing the template to the browser, the
importation APPENDS the stored file to the already present bookmarks in the
given browser session making duplicate entries.  This makes a mess that requires
hand-editing the duplicates. Every folder must be checked out also as its
contents may be more up to date than what is listed in the given browser in the
given session.

Reproducible: Always

Steps to Reproduce:
1.Open Bookmark Mgr
2.Click Import
3.Import Master Bookmark.html file from directory
4.The contents of the Master File are APPENDED to the already existing Bookmarks
making duplicates of what is already present in the bookmark Mgr.

Actual Results:  
The contents of the Master File are APPENDED to the already existing Bookmarks
making duplicates of what is already present in the bookmark Mgr.
When Exporting the Bookmarks from a browser session, the dialogue requests if
you want to "replace" the existing file.  Instead it APPENDS all of the existing
bookmarks in the pareticular browsing session to the Master File thereby making
duplicates in the Master HTML file as well.  It malfunctions in BOTH directions,
Import or Export

Expected Results:  
One should be able to Import only the bookmarks that are NOT PRESENT in the
bookmark the given user's bookmarks for a particular browser session.

I realize that this is what I WANT and I can write an addition to the source
that will match the $trings in the Master File and not Import/Export them to the
given user's browser.  I will if I get the time but it would be nice if it
worked properly without my intervention.  It's NOT really a "BUG" but an
important oversight.

Should I get around to re-Writing the Source to accomplish the above, I'll be
certain to send it to the proper place but where to send the work would the be best?

Product: Browser → Seamonkey


14 years ago
Assignee: bugs → p_ch
QA Contact: kasumi → bookmarks
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.