Closed Bug 203031 Opened 23 years ago Closed 23 years ago

TM should not be used in title bar

Categories

(Firefox :: General, defect)

x86
All
defect
Not set
normal

Tracking

()

VERIFIED FIXED

People

(Reporter: swillison, Assigned: bugs)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4a) Gecko/20030422 Firebird™ Browser/0.6 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4a) Gecko/20030422 Firebird™ Browser/0.6 On Win98 (haven't tried on other versions) the latest nightly has "Firebird[] Browser" in the application title bar, where the [] is one of those ugly squares that crop up in Windows when a character can't be rendered. I'm guessing that this is meant to be a ™. Reproducible: Always Steps to Reproduce: 1. Install the April 22nd nightly build of Firebird/Phoenix on a Win98 PC 2. Run it. 3. Look at the title bar. Actual Results: TM sign comes up as a square. Expected Results: TM sign should come up as a TM sign.
Changing summary. -> NEW TM is a character of machine (font) dependence. It should not be used in title bar. MacOS or WindowsMe also fails to paint.
Assignee: blaker → ben
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: TM shows up as a ugly square in the title bar → TM should not be used in title bar
using (tm) would just be plain ugly... either it's ™ or nothing, IMO?
In Linux the 'TM' is displaying as a '?'. I get a similar problem with the about: window as well in the UA string. OS --> All
OS: Windows 98 → All
Blocks: 202233
Another option could be "Mozilla Firebird" as the title 1) There is only ONE Firebird Browser, there is really no need to have the "Browser" part there 2) The places where "phoenix" has been replaced with "firebird" would still work 3) Would fix this bug We could still maintain the (tm) in the about dialog?
has been fixed with 20030423 as far as i know?
Pierre fixed this yesterday between 12.28 and 14.46
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.