Closed
Bug 505121
Opened 15 years ago
Closed 14 years ago
[SeaMonkey 2.1] Personal Toolbar misses its chevron on startup
Categories
(SeaMonkey :: Bookmarks & History, defect)
SeaMonkey
Bookmarks & History
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sgautherie, Unassigned)
References
Details
(Keywords: regression)
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.1pre) Gecko/20090711 SeaMonkey/2.0b1pre] (comm-1.9.1-win32-unittest/1247314938) (W2Ksp4) (http://hg.mozilla.org/releases/mozilla-1.9.1/rev/d3c7a48a5b6a +http://hg.mozilla.org/comm-central/rev/291cbe3374b9) No bug. [Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.2a1pre) Gecko/20090715 SeaMonkey/2.1a1pre] (home, optim default) (W2Ksp4) (http://hg.mozilla.org/mozilla-central/rev/d190d9b6ccd1 +http://hg.mozilla.org/comm-central/rev/773809454cf2 + bug 503724 patch) Maximized or not, the P.T. loads like it has "unconstrained width". Workaround: (un-)maximize the window. NB: Iirc, the regression is not recent.
Comment 1•15 years ago
|
||
There are several (fixed) Firefox bookmark toolbar chevron bugs. But I don't have the time to look through them to see if any are relevant.
Reporter | ||
Comment 2•15 years ago
|
||
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.2a1pre) Gecko/20090712 SeaMonkey/2.1a1pre] (nightly) (W2Ksp4) (http://hg.mozilla.org/mozilla-central/rev/628c8764ade1 +http://hg.mozilla.org/comm-central/rev/...) First Windows trunk nightly: already broken.
Thinking what you are seeing depends on the value of /shell.checkDefaultClient/. If shell.checkDefaultClient is True, on browser startup, for the first opened window (& tabs within) the chevron does not display. In subsequently opened windows, the chevron does display. If you resize the (first) window using the Maximize/Restore Down window icon, then the chevron will appear. (I did not check this is a SeaMonkey 2.1 build, but this does occur is SeaMonkey 2.0 release & 2.0.1 Candidate Build2.)
Edit | Preferences | Advanced -> System Integration => Check default applications settings on startup 1) Set shell.checkDefaultClient to False 2) Restart browser Personal Toolbar chevron appears. 3) Set shell.checkDefaultClient to True 4) (do not close the browser &) Open a new window After dismissing the Default Client dialog, the window loads, but the Personal Toolbar chevron is missing.
Regression: Broken: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1b3pre) Gecko/20081202 SeaMonkey/2.0a2pre Works: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1b3pre) Gecko/20081201 SeaMonkey/2.0a2pre http://hg.mozilla.org/comm-central/pushloghtml?startdate=2008-12-01&enddate=2008-12-02 So maybe a regression from Bug 453797 ?
Having just installed a 2.1a Trunk, 1.9.3a, I am seeing this on (almost) all windows, not just at startup. This is a different behavior from what I experienced on 2.0.x & is not affected by the shell.checkDefaultClient setting. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a5pre) Gecko/20100422 SeaMonkey/2.1a1pre (Perhaps this should be a new bug?)
Comment 7•15 years ago
|
||
(In reply to comment #0) > Workaround: (un-)maximize the window. You can also just resize the browser window. > NB: Iirc, the regression is not recent. That's what I remember, too. AFAIR this is really old. But as I also remember this did not appaear in some later 2009 builds. Seeing this also on Linux x86 and x86_64-> changing 'Platform'
OS: Windows 2000 → All
Hardware: x86 → All
This appears to have resolved itself over the last day or so. Mozilla/5.0 (Windows NT 6.1; rv:2.0b4pre) Gecko/20100817 SeaMonkey/2.1b1pre (I'll look tomorrow, or so, for a range.)
Comment 9•14 years ago
|
||
> (I'll look tomorrow, or so, for a range.)
How about when Place Bookmarks landed?
Comment 10•14 years ago
|
||
Uh, well yes. 2010-08-08 broken. 2010-08-09 works. http://hg.mozilla.org/comm-central/pushloghtml?startdate=2010-08-08&enddate=2010-08-09
Comment 11•14 years ago
|
||
Fixed in Bug 557496
No longer blocks: CcMcBuildIssues
Status: NEW → RESOLVED
Closed: 14 years ago
Depends on: 557496
Resolution: --- → FIXED
Updated•14 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•