Closed Bug 238193 Opened 21 years ago Closed 20 years ago

Mozilla fails some sections of CSS1 testsuite

Categories

(Core :: CSS Parsing and Computation, defect)

Product:
Core
Component:
CSS Parsing and Computation
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

()

Status:
RESOLVED EXPIRED

People

(Reporter: unknown_kev_cat, Assigned: dbaron)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316 One section that is failed is: http://www.w3.org/Style/CSS/Test/CSS1/current/sec21.htm Clicking the quoted word "anchor" causes the word to change color, apparently in violation of CSS1 http://www.w3.org/Style/CSS/Test/CSS1/current/sec411.htm seems to show 1cm as about 1 inch on my screen, not a bug. http://www.w3.org/Style/CSS/Test/CSS1/current/sec522.htm The font mozilla uses for the cursive font family on my system is not cursive, however the font used for the fantasy font family is cursive. This is likely a bug. http://www.w3.org/Style/CSS/Test/CSS1/current/sec525.htm The font weights seem to be rounded down, meaning that bold=bolder. And a weight of 500 or below is identical to normal. Only the first appears to be a bug of any real importance. Reproducible: Always Steps to Reproduce: 1. 2. 3.
(In reply to comment #0) > One section that is failed is: > http://www.w3.org/Style/CSS/Test/CSS1/current/sec21.htm > Clicking the quoted word "anchor" causes the word to change color, apparently in > violation of CSS1 No longer true in CSS2. > http://www.w3.org/Style/CSS/Test/CSS1/current/sec522.htm > The font mozilla uses for the cursive font family on my system is not cursive, > however the font used for the fantasy font family is cursive. This is likely a bug. > > http://www.w3.org/Style/CSS/Test/CSS1/current/sec525.htm > The font weights seem to be rounded down, meaning that bold=bolder. And a weight > of 500 or below is identical to normal. I think there are other bugs filed on both of these. Please try to keep one issue per bug.
I find it hard to belive that CSS2 introduces inconsistancies in the CSS1 testsuite, without w3 placing a warning as such in the test suite. Besides, CSS2 was inteneded to be fully compatable with CSS1.
(In reply to comment #1) > (In reply to comment #0) > > http://www.w3.org/Style/CSS/Test/CSS1/current/sec522.htm > > The font mozilla uses for the cursive font family on my system is not cursive, > > however the font used for the fantasy font family is cursive. This is likely a > bug. Bug 47752? > > http://www.w3.org/Style/CSS/Test/CSS1/current/sec525.htm > > The font weights seem to be rounded down, meaning that bold=bolder. And a weight > > of 500 or below is identical to normal. Bug 93725?
(In reply to comment #0) > http://www.w3.org/Style/CSS/Test/CSS1/current/sec525.htm > The font weights seem to be rounded down, meaning that bold=bolder. And a weight > of 500 or below is identical to normal. Actually, I don't think any of what you describe is a bug. Given fonts that have only two weights, bolder should be equivalent to bold, 100, 200, 300, and 500 should be equivalent to 400, and 600, 800, and 900 should be equivalent to 700. That said, we don't properly support the presence of fonts of more than two weights (as mentioned in comment 4).
(In reply to comment #0) > http://www.w3.org/Style/CSS/Test/CSS1/current/sec411.htm seems to show 1cm as > about 1 inch on my screen, not a bug. How big is your monitor, and at what resolution? Do you have Windows's "Large Fonts" option set? Did you set Mozilla's DPI pref?
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.