Closed Bug 245025 Opened 21 years ago Closed 21 years ago

Roaming does not check different bookmarks location

Categories

(Core Graveyard :: Profile: Roaming, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: InvisibleSmiley, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a2) Gecko/20040529 MultiZilla/1.6.4.0b Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a2) Gecko/20040529 MultiZilla/1.6.4.0b If you specified a different bookmarks file, Mozilla still uses the one from your profile for roaming. Reproducible: Always Steps to Reproduce: 1. Select another location for your bookmarks (e.g. via about:config) 2. Enable roaming 3. Activate roaming bookmarks (default) 4. Exit Mozilla Actual Results: The bookmarks.html file from your profile directory is used for roaming. Expected Results: The alternate location of your bookmarks file should be used for roaming.
I don't think there's much point in fixing this. Not all users might expect this behaviour, and it's a an edge case anyways, not even a UI for it (to my knowledge).
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WONTFIX
since you're roaming preferences, you should consider roaming the referenced file, otherwise you may end up causing mozilla to dump an empty file which will confuse the user more.
Component: Profile: BackEnd → Profile: Roaming
QA Contact: core.profile-manager-backend → core.profile-roaming
> since you're roaming preferences No, I don't. (Good point, though.)
I moved my bookmarks file back to my profile folder when this bug was marked WONTFIX. I originally moved it out of the folder only to be able to sync it via FTP together with my homepage anyway.
*** Bug 263196 has been marked as a duplicate of this bug. ***
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.