Bug 23744 – stylesheet not applied because css file not parsed correctly if it contains comments and charset

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: CSS

[jasneet]

I Steps:
Go to http://csdraveurs.qc.ca/

II Issue:
left navigation bar links have extra scroll bars

III Conclusion:
The issue is caused by the css file not being applied correctly because of the 
/*comment*/ and @charset in its contents. The css file looks like: 

/* Définition de règle */
@charset "iso-8859-1";
.leftframe {color: 0067c6; font-family:  "Times New Roman", Times, serif; font-size: 
10px; font-weight: bold; line-height: normal; text-align: center}

IV Other Browsers:
IE7: ok
FF3: ok

V Nightly tested: 40471

Bug in Chromium : http://code.google.com/p/chromium/issues/detail?id=5771

[jasneet]

Created attachment 27330 [details]
testcase

[Alexey Proskuryakov]

This is broken CSS - "@charset" should be the first bytes in file, except for BOM. But obviously, we should be more forgiving for compatibility with other browsers.

One thing we should test for is whether this charset is honored, or just ignored.

[Taruchhaya]

I have done some analysis on this bug.My observations are:

1) "leftframe.css" :: Issue is caused by the css file not being applied correctly because of the /*comment*/ and @charset in its contents. The css file looks like: 
/* Dfinition de rgle */
@charset "iso-8859-1";
.leftframe {color: 0067c6; font-family: "Times New Roman", Times, serif;
font-size: 10px; font-weight: bold; line-height: normal; text-lign: center}

Reason::The @charset At-Rule is allowed to occur only once in an external style sheet and it must be the very first statement in the style sheet. 

QUERIES:
1) "/*comment*/" is a valid CSS statement, which is escaped/ignored while executing the code. So shouldn't the same approach be followed in this case and @charset should be considered/honored.

While debugging the Grammar.y, I found that "/*comment*/" is not the issue. The issue is in "/r" & "/n" after the comment, which is forcing the parser to consider the rest of the document as an invalid rule.

2) I also found another issue in this bug,i.e. in "Link Tag".
Reason:: In Safari, Link Tag is not able to open/recognize the externally linked CSS file. 
As, HTML document contains the following snippet for link tag:
<link href="leftframe.css" rel="stylesheet" type="text/css">
<link href="../leftframe.css" rel="stylesheet" type="text/css"> 

Here, In second link statement: "../leftframe.css" is invalid because it is trying to access the .css file from the root level, which is not available, webkit should check this condition and then resolve it by appending to the base URI just like how IE does.

Please provide me some suggestions on the above issues.

[Alexey Proskuryakov]

(In reply to comment #3)
> 2) I also found another issue in this bug,i.e. in "Link Tag".

Please file a new bug for this new issue.

[Taruchhaya]

 Raised the new Bug ID: 24084:: "Link Tag" issue

[Alexey Proskuryakov]

See also: bug 18265 (@charset in inline CSS).

[Alexey Proskuryakov]

*** Bug 23947 has been marked as a duplicate of this bug. ***

[Adam Barth]

This is the same a Bug 18265 because the comment get stripped out by the tokenizer.

*** This bug has been marked as a duplicate of bug 18265 ***