Closed Bug 37621 Opened 25 years ago Closed 24 years ago

Bookmark in Bookmark panel not updated after editing location

Categories

(SeaMonkey :: Bookmarks & History, defect, P2)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: marc.loiselle, Assigned: waterson)

Details

(Whiteboard: [nsbeta2+][rjc] 7/11)

From Bugzilla Helper: User-Agent: Mozilla/4.7 [en] (X11; I; Linux 2.2.5-15 i586) BuildID: 20000428009 Editing a bookmark's location does not update bookmark in Bookmark panel. Reproducible: Always Steps to Reproduce: 1.open sidebar 2.select bookmarks panel 3.Select a bookmark with mouse 4.Right click on it and select properties 5.Change bookmark's location and click ok. 6.Open bookmark by double-clicking on it bookmark panel 7.Mozilla does not load the new location entered Expected Results: Bookmark location should be updated in panel. Toggling View->Sidebar seems to force a reload of bookmark information. Editing of bookmark name is shown immediately in panel.
Keywords: nsbeta2
Putting on [nsbeta2+] radar for beta2 fix.
Whiteboard: [nsbeta2+]
Confirmed with 2000-03-15-08 on Linux.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: P3 → P2
Target Milestone: --- → M16
Move to M18.
Target Milestone: M16 → M18
Added "rjc" to status whiteboard since we need Robert's help to fix this for beta 2 while slamm is on sabbatical.
Whiteboard: [nsbeta2+] → [nsbeta2+][rjc]
Chris, I'm guessing that this might be an issue with the template builder. Any ideas?
Sharing the luv... Chris, any thoughts re: the template builder?
Assignee: slamm → waterson
i'll take a look...
Status: NEW → ASSIGNED
Target Milestone: M18 → M17
Whiteboard: [nsbeta2+][rjc] → [nsbeta2+][rjc] 7/8
Whiteboard: [nsbeta2+][rjc] 7/8 → [nsbeta2+][rjc] 7/11
Oops. I lost the code to re-match rules in nsXULTemplateBuilder::OnChange(). Added it back, r=rjc.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
VERIFIED Fixe with 2000071008 builds
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.