Closed
Bug 103159
Opened 23 years ago
Closed 23 years ago
sorting fonts by foundry names cause font size of css ignored in some cases
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
RESOLVED
FIXED
Future
People
(Reporter: f300v10, Assigned: ftang)
References
()
Details
(Keywords: css1)
Attachments
(1 file)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4+) Gecko/20011002
BuildID: 2001100321
This just regressed on todays build, it works fine on 2001100221. On the above
page, the style properties of the table cell are set using a <td class='class in
style sheet'> Things like font-weight are working, but font-size is not. I
wish I could be more specific, but only some of the page is effected.
Reproducible: Always
Steps to Reproduce:
1.go to above URL
2.look at the daily averages and records table
3.it renders to wide and horks the page layout because the font-size is not that
specified in the css
Actual Results: font-size attribute is ignored
Expected Results: should use the correct css font-size
regressed relative to which previous build?
Reporter | ||
Comment 2•23 years ago
|
||
David, the build I first see it on is 2001100321 Linux. It is also on
2001100408. I have played around with this and the problem appears to be
specific to certain fonts and sizes. I will attach a test case that appears to
show the problem with the default linux mozilla font settings (at least on my
machine RH7.0). The problems I see are only if the font-size is set to 11,12 or
13px. Any other size works fine.
Reporter | ||
Comment 3•23 years ago
|
||
Reporter | ||
Comment 4•23 years ago
|
||
The test case I just posted is a table with 3 rows. Each row is a different
font, Arial, Helvetica, and Bookman, and each cell is set a different font-size,
8-15. On my machine Arial and Bookman show the bug where the 11,12 and 13
cells are identical in size. The Helvetica row looks correct.
All the rows look correct on my 2001100221 build. Hope this helps.
WFM on Windows.
Looks like a regression from bug 94327 which was indeed checked-in in Oct 2 --
saw that it is re-opened and a backout is being considered.
Depends on: 94327
->bstell, based on rbs's investigation.
Assignee: dbaron → bstell
Comment 7•23 years ago
|
||
Uhm... AFAIK the patches in bug 94327 require to wipe-out the font names in
prefs.js (I simply deleted ~/.mozilla), otherwise you'll see some weired
effects...
Did anyone try that ?
Reporter | ||
Comment 8•23 years ago
|
||
Roland,
I took your advise and created a new profile from scratch. It made no difference.
Reporter | ||
Comment 9•23 years ago
|
||
I just grabbed this mornings linux build 2001100506 which has the patch for bug
94327 backed out, and the problem here is gone. So 94327 sure seems to be the
cause.
Updated•23 years ago
|
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → Future
Comment 10•23 years ago
|
||
Why the heck is this future? Font size style is totally fucked in 0.9.5 on
Linux. All the fonts are the same size regardless of specified size.
Severity: normal → major
Keywords: css1
Are any of you using the Debian packages of Mozilla rather than the mozilla.org
distributions?
Reporter | ||
Comment 12•23 years ago
|
||
I just installed and tested this on 0.9.5 on linux (2001101202) and I do not see
the bug using my test case. The patch for 94327 was the original cause of this
bug, and it was backed out both on the trunk and on the .95 branch.
Comment 13•23 years ago
|
||
I am using the debian packages. I saw this message on debian-user:
http://lists.debian.org/debian-user/2001/debian-user-200110/msg02474.html
...but there was no indication that the bug lies in debian.
(time passes)
Aha! It was those chowderheads at debian who inserted this bogosity into the
latest packages:
pref("font.minimum-size.x-western", 14);
This line isn't in Mozilla's copy of unix.js. Bug 115842 has been filed against
Debian. Sorry about that.
Comment 14•23 years ago
|
||
This bug was side-tracked with the debian stuff. The original problem is
documented by earlier comments.
FWIW, the Debian report is at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=115842
Comment 16•23 years ago
|
||
Updating title for clarification.
Summary: Font size of css ignored in some cases → sorting fonts by foundry names cause font size of css ignored in some cases
Comment 17•23 years ago
|
||
I suspect this is a dup of bug 94327
I checked in a fix on 10/02 but due to the closeness of the release I
backed it out on 10/04
Reporter | ||
Comment 18•23 years ago
|
||
Brian, this is not a dupe of bug 94327, it was caused by the patch for 94327.
This bug went away as soon as the patch was backed out. As I said when I
originally reported the bug, the first build I tried with this problem was
2001100321. The bug has been gone since build 2001100506.
Comment 19•23 years ago
|
||
being a side effect of bug 94327 it should be handled under that bug
Comment 22•23 years ago
|
||
I've checked in a new version of the patch for bug 94327.
Scott, wanna verify that this issue has been fixed with the new patch ?
Comment 23•23 years ago
|
||
I can verify that it hasn't been fixed. Truetype fonts on Linux are completely
ignored now, both in preferences as well as on pages using CSS. It looks like
shit, I assure you. Readability on pages like cnn.com and msn.com just went down
the drain. Font choises there suddenly look hopelessly clumsy compared to what
the pages used to look like when they were allowed to use fonts they were
primarily designed for.
Comment 24•23 years ago
|
||
R.K.Aa wrote:
> I can verify that it hasn't been fixed. Truetype fonts on Linux are completely
> ignored now, both in preferences as well as on pages using CSS.
... which was simply a problem that the hardcoded font ban was rejecting
outline-scaled fonts, too. I fixed that in the new patch by explicily turning
the font ban OFF for outline scaled fonts ...
Reporter | ||
Comment 25•23 years ago
|
||
Roland,
Everything looks good using nightly build 2001120321. So assuming this build
has your latest patch (I could not tell looking at the cvs tree) then this can
be marked as fixed.
Reporter | ||
Comment 26•23 years ago
|
||
This was fixed a while back, marking as such.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•