Closed
Bug 231099
Opened 22 years ago
Closed 22 years ago
"font" property of css is not parsed
Categories
(Core :: DOM: HTML Parser, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: xces, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040114 Firebird/0.7+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040114 Firebird/0.7+
If a stylesheet is external (<link rel="..." />) and this external file contains
the <style type=".."> tag (which it shouldn't but ok..) then some properties
don't get rendered in the nightly build of Firebird 0.7+ (downloaded 15-01-2004)
Reproducible: Always
Steps to Reproduce:
--------------------
This snipet:
--------------------
<html><head><link rel="stylesheet" href="./style.css"
/></head><body>...</body></html>
--------------------
This text in the external CSS (Fails)
--------------------
<style type="text/css">
<!--
body, p, td, tr, ol, ul {
font: 10pt verdana, geneva, lucida, 'lucida grande', arial, helvetica, sans-serif;
}
//-->
</style>
Actual Results:
If a malformed external CSS file is given (hence the "<style ..." tag), what i
tested is that color and background-color work, but not all definitions work
(e.g. the "font" property is skipped)
Expected Results:
If the background-color and the color tags work, then why not the "font" tag?
|
||
Updated•22 years ago
|
Assignee: blake → parser
Component: General → HTML: Parser
Product: Firebird → Browser
Version: unspecified → Trunk
|
|
||
Comment 1•22 years ago
|
||
"and this external file contains the <style type=".."> tag (which it shouldn't but ok..)"
Not OK. The details of *why* it works this way has to do with forward-compatibility in CSS parsers;
the "<style" is interpreted as the beginning of a style rule, which isn't closed until the brace is
closed at the end of the first rule, or something along those lines.
And this has nothing to do with the HTML parser.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•