Closed Bug 84272 Opened 23 years ago Closed 14 years ago

UI needed for bookmarks.import_system_favorites preference (Import IE favorites)

Categories

(SeaMonkey :: Bookmarks & History, defect)

x86
Windows NT
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: matthew, Unassigned)

References

Details

Attachments

(4 files)

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0b; Windows NT 4.0)
BuildID:    2001060320

Bug 22642 added functionality for the user to choose whether to import their 
system favourites with the browser.bookmarks.import_system_favorites 
preference. This needs a UI.

In 22642 Ben said:

"Here's the solution I want: 

No preferences panel UI. This is more of a view option than a checkbox in 
prefs. 

Show the folder by default. Allow the user to delete it, perform a delete and 
then update the pref. Have a menu item in the view menu maybe, with platform 
text:

[x] Internet Explorer Favorites (Windows and Mac). 
[ ] NetPositive Favorites (BeOS)"
*** Bug 84281 has been marked as a duplicate of this bug. ***
Show/hide IE favs is something a given user with likely "fundamentally" want or
"fundamentally" not want.

Therefore, I'm not sure it makes sense to clutter up the menu (high traffic
area) with a selection that will rarely be used. It might be more suitable in
the prefs (low traffic area) since this setting is likely to be made only once
per user.

If it must be in the menu, I suggest to put it under:
View -> Show/Hide -> Internet Explorer Favorites
My understanding is that this would be in the Bookmarks Manager View menu, not 
the main browser view menu.

(Patch to follow.)
The above patches allow for platform-specific overlays in order to create an 
option View -> [whatever] Favorites in Bookmarks Manager. I have attached 
Windows versions of the new files.
*** Bug 85201 has been marked as a duplicate of this bug. ***
Adding that bit to the end of the summary because I searched for IE in the
component 'bookmarks' to see if this bug was already filed and because it didn't
show up I filed a duplicate, so this may stop other people doing the same. 
Summary: UI needed for bookmarks.import_system_favorites preference → UI needed for bookmarks.import_system_favorites preference (Import IE favorites)
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.1
Paul Chen is now taking Bookmarks bugs. For your convenience, you can filter 
email notifications caused by this by searching for 'ilikegoats'.

Assignee: ben → pchen
Status: ASSIGNED → NEW
mass reassign of pchen bookmark bugs to ben
Assignee: pchen → ben
Blocks: 120814
Status: NEW → ASSIGNED
Target Milestone: mozilla1.1 → Future
Matthew, does your patch still work? Why is this bug futured when it has a patch?
Does this pref even work now? I have it in my prefs.js, but it seems to have
stopped working with the 2002-02-21 Win32 build...
Keywords: nsbeta1nsbeta1-
Blocks: 123569
*** Bug 152106 has been marked as a duplicate of this bug. ***
*** Bug 171360 has been marked as a duplicate of this bug. ***
suggest renaming this so that it is distinct from bug 59636.  For instance, how
about: "Need UI to update 'Imported IE Favorites' bookmarks
[import_system_favorites preference]"?
___________________________________________

Also, I have also made comments on the other bug (which I think is about
permanent conversion of IE Favorites) and on bug 56765 about the continuing
confusion in goals for Mozilla's IE/Windows integration.  For instance, in the
current Phoenix 2002-10-28 (which I assume it working the same as Mozilla's
bookmarks?) the 'Imported IE Favorites' bookmarks are now editable ... but still
don't "push" their changes back to IE.  I want to be able to switch
back-and-forth between IE and Mozilla without losing the ability to share IE
Favorites.  So, making the imported bookmarks permanent is a setback to me.  See
my comments on bug 56765 for more specific comments.
*** Bug 197104 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
Assignee: bugs → nobody
Status: ASSIGNED → NEW
QA Contact: claudius → bookmarks
Target Milestone: Future → ---
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
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
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
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
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
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
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
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
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: