Open
Bug 655180
Opened 14 years ago
Updated 2 years ago
incorrect spacing between T and small letter in Times New Roman
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: rog3rli, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
I'm not sure if my computer or font thing is messed up, but in Times New Roman font in Firefox, such as address or search bar (maybe other fonts not sure) if you type certain letters together it gets squeezed together, bad spacing.
It's fairly obvious because the spacing is larger in something like MSWord
sequences like Ta, Tc, Te, Tr and probably more
Reproducible: Always
Steps to Reproduce:
1.just go to the search bar or whatever
2.type in Tr
3.
Actual Results:
Tr is squeezed together incorrectly, the r is below the T, in the right "caved in" part
Expected Results:
normal spacing
Comment 1•14 years ago
|
||
Please attach a screenshot showing the issue.
Does the issue still occur if you start Firefox in Safe Mode? http://support.mozilla.com/en-US/kb/Safe+Mode
Note that kerning is enabled by default in Fx4
http://en.wikipedia.org/wiki/Kerning
Comment 3•14 years ago
|
||
Reporter -> Are you still experiencing this issue? Have you tried safe mode and captured a screenshot?
Comment 5•14 years ago
|
||
Does this happen in text boxes (like this comment field) or other locations, or only in the search bar?
it seems to happen on the Firefox bars. I'm not good at terminology, but what I mean is. the spacing is always fine on webpages textboxes and input fields and stuff. by bars I mean anything that is an input field for firefox i guess? like if I bookmark something, the glitch happens in the input fields, but if I input something into the google search bar, its fine. though that may be google's formatting or something
I doubt it'll happen in monospace formatted input fields
Comment 7•14 years ago
|
||
And it occurs in safe mode and a new profile?
Does it occur in the location bar (the place that shows the URL [https://bugzilla.mozilla.org] as an example)?
Can you upgrade to FF 5 and see if it continues?
See also bug 646403
Component: General → Layout: Text
Product: Firefox → Core
QA Contact: general → layout.fonts-and-text
Version: 4.0 Branch → Trunk
Comment 10•14 years ago
|
||
Dup of bug 587297?
![]() |
||
Comment 11•13 years ago
|
||
Does this problem go away if harfbuzz is disabled?
Comment 12•13 years ago
|
||
Note that the font shown in the screenshot is *not* Times New Roman, as claimed. It's probably Tahoma.
Reporter | ||
Comment 13•13 years ago
|
||
well, i was never really good with fonts, all I knew was that it looked buggy.
Reporter | ||
Comment 14•13 years ago
|
||
and I tried both ff5 and ff6, no difference
Comment 15•13 years ago
|
||
Comment 16•13 years ago
|
||
Apologies for the double post, not familiar with how Bugzilla works yet. :(
The bug as initially described is still present in Firefox 9 running on an English Windows XP SP3. Also, it's barely noticable, but the pages being rendered are also subject to this bug in addition to Firefox's GUI itself.
Profiles do not seem to be a factor as I also experience the same bug on Pale Moon 8 (an unofficial fork based on Firefox 8, which also had the bug) with a new profile there.
Any attempts to disable what I presume the bug to be ligature via userChrome.css has proven fruitless. Is this bug being fixed any time soon?
![]() |
||
Comment 17•13 years ago
|
||
See also https://bugzilla.mozilla.org/show_bug.cgi?id=639185#c5
The Pref is now called "gfx.font_rendering.harfbuzz.scripts".
Comment 18•13 years ago
|
||
This problem is confirmed to STILL EXIST under Firefox 10.0 final release under Windows XP SP3 (32bit)
Please see my post here
http://forums.mozillazine.org/viewtopic.php?f=9&t=2302745
If I set harfbuzz to 2 instead of the default 3, the problem goes away.
Updated•2 years ago
|
Severity: trivial → S4
You need to log in
before you can comment on or make changes to this bug.
Description
•