Closed Bug 307115 Opened 19 years ago Closed 19 years ago

cannot open bookmark folder on personal toolbar in new windows

Categories

(Core :: XUL, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: baffclan, Assigned: jag+mozilla)

References

(Depends on 1 open bug)

Details

(Keywords: regression)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050904 SeaMonkey/1.1a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050904 SeaMonkey/1.1a

cannot open bookmark folder on personal toolbar

Reproducible: Always

Steps to Reproduce:
1. several bookmark folder put on personal toolbar
2. open web page (ex. http://www.mozilla.org/)
3. click a link, open a new window
4. on new window, cannot open bookmark folder on personal toolbar
I reproduced this with a one day-ish old build, but when I upgraded to the
latest Tinderbox build I don't see it anymore. Can you reproduce this each time
you open SeaMonkey? Is there a specific link that you're clicking on that causes
this? 
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → Trunk
(In reply to comment #1)
> Can you reproduce this each time you open SeaMonkey?
yes, I can reproduce with SeaMonkey/2005090406-trunk/WinXP.

> Is there a specific link that you're clicking on that causes this? 
not a specific link, it reappers with an arbitary link.

Reproducible with SeaMonkey/20050903, WFM with SeaMonkey/20050902.
cannot reproduce with SeaMonkey/2005090806-trunk/WinXP.
WORKSFORME?
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
reproduce with SeaMonkey/2005092105-trunk/WinXP.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Modifying summary and confirming. Not a bookmark bug - belongs in tabbrowser or
thereabouts.

The bug is still there in trunk 2005092205 SeaMonkey (for installation
workaround see bug 308838)
Assignee: p_ch → nobody
Status: UNCONFIRMED → NEW
Component: Bookmarks → Tabbed Browser
Ever confirmed: true
Product: Mozilla Application Suite → Core
QA Contact: bookmarks → tabbed-browser
Summary: cannot open bookmark folder on personal toolbar → cannot open bookmark folder on personal toolbar in new windows
Keywords: regression
> Not a bookmark bug - belongs in tabbrowser or thereabouts.

hmm... how so?  I can reproduce even when hiding tab bar.
*** Bug 310866 has been marked as a duplicate of this bug. ***
To comment #7:
yeah.. it's much more like "thereabouts"... XP Toolkit/Widgets: XUL?
Toolkit/Widgets for now
Assignee: nobody → jag
Component: Tabbed Browser → XP Toolkit/Widgets
QA Contact: tabbed-browser → jrgmorrison
*** Bug 310984 has been marked as a duplicate of this bug. ***
hmm... I can't reproduce this with builds up to and including 2005092005, but
that's obviously too late considering this bug was filed Sep 5.  Perhaps I'm
missing something in my profile that triggers the bug in earlier builds.

In a debug build, I get these whenever opening a new window:
###!!! ASSERTION: node in map twice: 'Not Reached', file
/build/andrew/moz-debug/mozilla/layout/base/nsFrameManager.cpp, line 1632
###!!! ASSERTION: unexpected second call to SetInitialChildList: 'Not Reached',
file /build/andrew/moz-debug/mozilla/layout/generic/nsContainerFrame.cpp, line 108
WARNING: Warning add child failed!!
, file /build/andrew/moz-debug/mozilla/layout/xul/base/src/nsBoxFrame.cpp, line 205
What I was seeing was a result of the patch from bug 307160, which was just
backed out (trunk + branch).  Please retest with todays builds.
(In reply to comment #12)
cannot reproduce with SeaMonkey/2005100405-trunk/WinXP.

Possibly related to bug 310187.
ok.  resolving FIXED by the backout of 307160 (and/or bug 285076, which was also
backed out).  I started seeing this with the checkin from bug 307160, but others
might have been seeing this as a regression from bug 285076.
Status: NEW → RESOLVED
Closed: 19 years ago19 years ago
Depends on: 307160
Resolution: --- → FIXED
So this was basically bug 310833, sounds like....
You need to log in before you can comment on or make changes to this bug.