116362 - Separators lose position in recent build

Status: RESOLVED WORKSFORME

(SeaMonkey :: Bookmarks & History, defect)

Description

[xyzzy]

I just grabbed build 2001121909, and on Windows 98, all of the separators in my
bookmarks seem to have floated to the top of their respective folders, losing
their placement within the folders.

Hopefully this is not due to the recent checkin for bug 114215.  This is highly
visible and results in data loss.

Comment 1

[xyzzy]

New serparators are generated at the bottom of the root folder, and don't seem
to be movable now either...

Comment 2

[Peter Trudelle]

mass reassign of pchen bookmark bugs to ben

Comment 3

[Waldemar Horwat]

Also happens on Mac.  All separators have floated to the top of the bookmark
menus and submenus.  All folders have also been relocated in the bookmark menus,
making most of them unintelligible.
mozilla1.1 is too late to fix this recent regression.  This is a dogfood issue.

Comment 4

[Waldemar Horwat]

This is a regression since the Jan 11, 2002 build, which worked properly for me.

Comment 5

[Waldemar Horwat]

*** Bug 121598 has been marked as a duplicate of this bug. ***

Comment 6

[Waldemar Horwat]

According to bug 121598, this is a regression from yesterday.

Comment 7

[Jason Kersey]

I started seeing this in 2002-01-24-03

Comment 8

[xyzzy]

waldemar,

My original report shows that this has been an issue for me since late December,
not just yesterday.  Perhaps it was just less broken before yesterday?

Comment 9

[Christopher Aillon (sabbatical, not receiving bugmail)]

waldemar, I don't think this is the same bug as recently duped bug 121598. This
bug has been ongoing for quite some time and also causes dataloss.  Bug 116362
does not and it just started occuring recently.  The bookmarks.html file is fine
in 116362 if you revert to an older build - everything is still in the proper
order.  Here in this bug it apparently does not.

Comment 10

[Martin Poirier]

for me I saw this before, november-december, then it was fixed since a month or
so, but It reappeared with 2002012403

Comment 11

[xyzzy]

Bug 121777 is probably related to yesterday's regression reported as bug 121598,
duped against this.

Comment 12

[Waldemar Horwat]

Seems to be working again in today's build.

Comment 13

[xyzzy]

Yes, now that I've gotten 2002020409, WFM.

Comment 14

[Diego Biurrun]

wfm Linux 2002011208, marking WORKSFORME, reopen if necessary.