Closed
Bug 368418
Opened 18 years ago
Closed 18 years ago
QuickLaunch - app startup pref ignored
Categories
(Core Graveyard :: QuickLaunch (AKA turbo mode), defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: csthomas, Assigned: neil)
References
Details
(Keywords: fixed-seamonkey1.1.1)
Attachments
(1 file)
573 bytes,
patch
|
csthomas
:
review+
Biesinger
:
superreview+
|
Details | Diff | Splinter Review |
In SM1.1., with QuickLaunch running, no matter what boxes are checked under Appearance->"When SeaMonkey starts up, open", a shortcut that runs seamonkey.exe with no arguments results in a browser only.
Updated•18 years ago
|
Assignee: general → quicklaunch
Component: General → QuickLaunch (AKA turbo mode)
Product: Mozilla Application Suite → Core
QA Contact: general
Assignee | ||
Comment 1•18 years ago
|
||
OK, so the issue here is that seamonkey -turbo needs to inhibit the default preferences. It does this by setting an mShouldShowUI flag to false, but this flag never gets set to true again. This wasn't a problem in 1.0.x because bug 58523 changed the order of startup tests and this code only used to run once.
Assignee | ||
Comment 3•18 years ago
|
||
Comment on attachment 255587 [details] [diff] [review]
Proposed patch
See previous comment...
Attachment #255587 -
Flags: superreview?(jag)
Attachment #255587 -
Flags: review?(cst)
Attachment #255587 -
Flags: review?
Reporter | ||
Comment 4•18 years ago
|
||
Comment on attachment 255587 [details] [diff] [review]
Proposed patch
I think this fixed bug 368421 too.
Attachment #255587 -
Flags: review?(cst) → review+
Comment 5•18 years ago
|
||
suspect there is _at least_ one, much older dupe. sorry, i read quite of few but don't have number(s)
Comment 6•18 years ago
|
||
Comment on attachment 255587 [details] [diff] [review]
Proposed patch
could you diff with more context and -p in the future?
Attachment #255587 -
Flags: superreview?(jag) → superreview+
Updated•18 years ago
|
Keywords: fixed-seamonkey1.1.1
Reporter | ||
Comment 11•18 years ago
|
||
Any reason this bug isn't marked as resolved?
Assignee | ||
Comment 12•18 years ago
|
||
(In reply to comment #11)
>Any reason this bug isn't marked as resolved?
Because I was checking with KaiRo as to whether it would make 1.1.1 and overlooked that he'd only set the 1.1.1 flag and not resolved it too.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•