45577 - import should merge folder contents for folders with same name at same level

Status: RESOLVED EXPIRED

(SeaMonkey :: Bookmarks & History, enhancement)

Description

[Devoti Paolo]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; m17) Gecko/20000713
BuildID:
20000071320

After importing navigator4.73 bookmarks, whithin the sidebar bookmark view, drag the imported
personal toolbar folder just before the current one. crash

Reproducible: Always
Steps to Reproduce:
1.import
the bookmarks
2.get in the sidebar bookmarks view 
3.drag the imported personal bookmark
folder just before the current one

Actual Results:  crash

Expected Results:  no crash and
possibly, since they have the same name, the merge of the two folders

Comment 1

[leger]

Adding crash keyword

Comment 2

[Chris McAfee]

m18

Comment 3

[Asa Dotzler [:asa]]

what do you mean by "import the bookmarks"?  Are you migrating a 4.x profile? 
what do you mean by "the current one"? What is this second folder?

I migrated a profile. 
I moved teh personal toolbar folder to every location possible in the sidebar 
bookmarks panel
I was unable to crash.

Comment 4

[Devoti Paolo]

By import the bookmarks I mean: manage bookmarks>file>import bookmarks
then select bookmarks.htm from a NN4.7 installation
The current one is the "Personal toolbat folder" that was there before 
importing the bookmarks.
I'm going to verify with the current build if is still crashing on my pc.

Comment 5

[Devoti Paolo]

It is slow but there is no crash with (win98 2000072008)
Is only left open the question about merging or not the folders with same name

Comment 6

[brad]

no crash but it's pretty easy to get the "manage bookmarks" list to be different
from the sidebar "bookmarks" list, by importing a set of bookmarks twice and
moving around the duplicated folders. The moving around is also very slow.

I believe that the folders should be merged. It's unheard of to allow folders
with the same name to exist at the same level.

Comment 7

[Claudius Gayle]

so the key here is it should not be possible to create dupes at the same level. The duplicates should be appended with .1 or 
something. Alternatively, imported bookmarks could be imported into their own folder so that they could never be at the same 
level, and a user could arrange them as they saw fit later.

Comment 8

[Devoti Paolo]

Going a little further:
Imported bookmarks should be imported into their own new folder
Do not allow folders with the same name to exist at the same level
When moving folders if you find at the same level one with the same name 
offer to merge or cancel the action
When merging if bookmarks with same link and description are found drop the 
duplicate

And probably is correct to remove the crash keyword

Comment 9

[Peter 'Rufus' Nelson]

Changing title to 'merge folders with same name on same level', adding [RFE],
setting severity to enhancement, setting os/plat to all, and removing target
milestone.

damn that's a lot...

Comment 10

[Karl Ove Hufthammer]

Reassigning to default component owner since slamm isn't here anymore.

Comment 11

[Marcia Knous [:marcia]]

Netscape Nav triage team: this is a Netscape beta stopper.

Comment 12

[Claudius Gayle]

If this is a 'Netscape Beta stopper' (doubtful) then it shouldn't be futured and vice-versa.

Comment 13

[Paul Chen]

nav triage team:

Not a beta stopper anymore. ;-) Marking nsbeta1-

Comment 14

[Ben Goodger (use ben at mozilla dot org for email)]

Paul Chen is now taking Bookmarks bugs. For your convenience, you can filter 
email notifications caused by this by searching for 'ilikegoats'.

Comment 15

[Peter Trudelle]

mass reassign of pchen bookmark bugs to ben

Comment 16

[Robert Kaiser]

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

Comment 17

[Robert Kaiser]

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

Comment 18

[Robert Kaiser]

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

Comment 19

[Robert Kaiser]

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

Comment 20

[Robert Kaiser]

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

Comment 21

[Robert Kaiser]

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

Comment 22

[Robert Kaiser]

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

Comment 23

[Robert Kaiser]

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