Closed Bug 238190 Opened 21 years ago Closed 20 years ago

Default Browser Dialog>" Check at startup next time, too" is weird

Categories

(Firefox :: General, defect)

defect
Not set
trivial

Tracking

()

RESOLVED FIXED

People

(Reporter: Lil46john, Assigned: bugzilla)

References

Details

(Keywords: fixed-aviary1.0)

I don't think that's good wording. It's like saying, Do you want popcorn, too? or Do you want, too, fly? The comma should be erased. Also, wording like "Always check when Firefox is not the default browser" woul be better
The comma does look odd, and the wording is a little screwy. My suggestions before I wait and see what's decided: Check (on|at) every startup. Check whether &brandShortName; is the default browser (on|at) every startup. I'm not sure which (on or at) is proper grammar, so I'd say go for the one that's proper grammar. (For those who don't know, &brandShortName; is equivalent to "Firefox".) This is really a trivial issue; it's reasonably understandable the way it is now.
Severity: normal → trivial
OS: Windows 2000 → All
Hardware: PC → All
Here's my suggestion, based on IE: "Always perform this check when starting Mozilla Firefox."
What about: "Let &brandShortName; check whether it is the default browser when starting." At least it fits on one line :). ~Grauw
Ah, sorry, I was talking about the phrase in preferences.
Blocks: 214267
No longer blocks: 214267
Blocks: 214267
Keywords: fixed-aviary1.0
"Firefox should check to see if it is the default browser when starting." This is how it appears on mine Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040812 Firefox/0.9.1+ (bangbang023) Should this be marked as fixed, or is there still discussion on how to get it onto one line or something?
It has the keyword fixed-aviary1.0 already, so it's not surprising that you see it fixed. However, my guess is that it has not been checked into the trunk yet, which would explain why the bug hasn't been marked as FIXED.
Fixed by branch landing.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.