Closed
Bug 87028
Opened 23 years ago
Closed 23 years ago
Improve wording about Turbo mode in Preferences
Categories
(SeaMonkey :: Preferences, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: doctor__j, Assigned: bhart)
References
Details
Attachments
(2 files)
1.01 KB,
patch
|
Details | Diff | Splinter Review | |
1.02 KB,
patch
|
Details | Diff | Splinter Review |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.1+) Gecko/20010620 BuildID: 2001062009 The current wording, "(reboot required)" is easily mistaken by user (or just me only?!) that Mozilla will reboot the machine after closing Pref menu, just like what usually happens after installing/uninstalling softwares. Suggestion: "(Effective after reboot)" "(Effective after you have rebooted)" The suggested wording is intended to emphasize the fact that you *CAN* keep on using the browser and there's no rush to reboot the system, or, to put it the other way round, Mozilla will not FORCE a reboot.
Another suggestion? -(Effective after reboot) +(Effective after your next reboot)
Ah... "(Effective after your next reboot)" sounds very nice... Cool... I'll vote for this one.
Comment 3•23 years ago
|
||
which prefs panel does the turbo stuff live in? couldn't find it in Advanced, then again i'm using 2001.06.20.15 bits...
Assignee: sgehani → vishy
QA Contact: sairuh → paw
Summary: Improve wording about Turbo mode in preference menu. → Improve wording about Turbo mode in Preferences
Comment 4•23 years ago
|
||
scratch that last comment --silly me, -turbo ain't in unix builds. :) anyhow, do see it in today's win32 bits...
Assignee | ||
Comment 6•23 years ago
|
||
Comment 7•23 years ago
|
||
r=sairuh, if you change it to "Enable Quick Launch (effective after restarting your computer)"
Assignee | ||
Comment 8•23 years ago
|
||
Comment 9•23 years ago
|
||
sr=darin
Fix checked in: C:\moz_src\mozilla\xpfe\components\prefwindow\resources\locale\en-US>cvs commit -m "87028 - Improve wording about Turbo mode in Preferences. Patch by Bradley H art <bhart00@yahoo.com> r=sairuh@netscape.com sr=darin@netscape.com" pref-advanc ed.dtd Checking in pref-advanced.dtd; /cvsroot/mozilla/xpfe/components/prefwindow/resources/locale/en-US/pref-advanced .dtd,v <-- pref-advanced.dtd new revision: 1.18; previous revision: 1.17 done
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 11•23 years ago
|
||
stephend, i presume your checkin was trunk-only? just a-wonderin'. is there a huge call for this to get this into the branch as well? paul, lisa, your thoughts?
Trunk only, for sure.
Comment 13•23 years ago
|
||
Would be good for limbo on branch. I'll mark nsBranch. Stephen, can you check into branch or find someone to do so when the time is appropriate?
Keywords: nsBranch
Assignee | ||
Comment 14•23 years ago
|
||
I have e-mailed drivers asking for a= to check this into the 0.9.2 branch.
Assignee | ||
Comment 15•23 years ago
|
||
Asa informs me that 0.9.2 is no longer accepting checkins, so I guess this missed the branch :-( Is it still possible to get this into a commercial branch?
Comment 16•23 years ago
|
||
Yes, it is possible. To be consistent in tracking this, I'm going to reopen this bug and add "vtrunk" keyword. This will indicate that the bug is fixed on the trunk, but waiting for branch checkin after PDT approval. (This all happens after mozilla 0.9.2 milestone is out.)
Bhuvan said he's check this in for me, thanks Bhuvan!
Assignee | ||
Comment 18•23 years ago
|
||
I have sent mail to pdt2@netscape.com, asking for a= to check this in.
Comment 19•23 years ago
|
||
I cannot approve this at this time. Final kit went out on Friday and this is a polishing fix. Please, don't check it into the branch, just the trunk.
Assignee | ||
Comment 20•23 years ago
|
||
oh, well. Marking fixed since this is already in the trunk.
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
Updated•23 years ago
|
QA Contact: paw → tpreston
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•