Closed Bug 368418 Opened 18 years ago Closed 17 years ago

QuickLaunch - app startup pref ignored

Categories

(Core Graveyard :: QuickLaunch (AKA turbo mode), defect)

1.8 Branch
x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: csthomas, Assigned: neil)

References

Details

(Keywords: fixed-seamonkey1.1.1)

Attachments

(1 file)

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.
Assignee: general → quicklaunch
Component: General → QuickLaunch (AKA turbo mode)
Product: Mozilla Application Suite → Core
QA Contact: general
Attached patch Proposed patchSplinter Review
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: quicklaunch → neil
Status: NEW → ASSIGNED
Attachment #255587 - Flags: review?
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?
Comment on attachment 255587 [details] [diff] [review]
Proposed patch

I think this fixed bug 368421 too.
Attachment #255587 - Flags: review?(cst) → review+
suspect there is _at least_ one, much older dupe. sorry, i read quite of few but don't have number(s)
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+
Any reason this bug isn't marked as resolved?
(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: 17 years ago
Resolution: --- → FIXED
Verifying based on user feedback.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: