55619 2011-03-02 14:43:47 -0800 Stylesheet rule cssText is all lowercase 2011-09-16 00:39:49 -0700 1 1 1 Unclassified WebKit CSS 528+ (Nightly build) All All RESOLVED WONTFIX http://tinymce.moxiecode.com/safari/stylesheet_case.html P4 Major --- 1 spam webkit-unassigned ap eric hyatt k_bolisetty mustaf.here rniwa sarap.karthik simon.fraser oldest_to_newest 361089 0 spam 2011-03-02 14:43:47 -0800 Description: The stylesheet rules are forced into lowercase. It should retain the case that is specified in the CSS file. Steps to reproduce: 1. Open the attached url. 2. Click the test button. 3. Observe that the CSS rule text is all lowercase instead of the original values. Expected result: The CSS rule should be the same case as the one inside the stylesheet. Actual result: The CSS rule is forced into lowercase it's not impossible to get the original case for a class. 361256 1 rniwa 2011-03-02 17:44:43 -0800 I suspect that fixing this bug requires considerable amount of work. 361264 2 simon.fraser 2011-03-02 17:51:48 -0800 I don't think any spec requires that case is round-tripped. 432178 3 sarap.karthik 2011-07-05 03:08:38 -0700 This issue is because of the rule we have for class: in CSSGrammar.y in the following lines if (!p->m_strict) $2.lower(); While loading the page, the call flow is CSSStyleSheet::parseStringAtLine() => CSSParser::parseSheet()=> cssyyparse(this); And while parsing as per the above logic, we convert the class string to lower case if the parser is running in NON-strict mode We have verified that if we add DOCTYPE on top of my html (which makes the CSSParser in strict mode), the style class info is shown maintaining proper casing given in the html page. Therefore, Does any one know why do we have that logic(as mentioned above) of converting string to lowercase for non-strict mode in CSSGrammar.y? Based on this, we can decide whether or not to fix the issue 432317 4 eric 2011-07-05 10:28:21 -0700 It's a documented quirk of Mozilla's quirks mode: https://developer.mozilla.org/en/mozilla_quirks_mode_behavior 432318 5 eric 2011-07-05 10:29:13 -0700 Or rather the case-insensitivity is: In quirks mode css class names are case insensitive. In standards mode they are case sensitive. 432321 6 rniwa 2011-07-05 10:31:26 -0700 class name is nothing to do with this bug. This bug is about cssText being lower case. 432633 7 mustaf.here 2011-07-05 23:11:59 -0700 (In reply to comment #5) > Or rather the case-insensitivity is: > > In quirks mode css class names are case insensitive. In standards mode they are case sensitive. My interpretation is if a html page does not mention any DOCTYPE, then it is by default quirks mode, correct? Then does it mean Mozilla has an issue here because in quirks mode also FF is respecting the CSS class names, which it should not do as per link given above? 468356 8 107614 k_bolisetty 2011-09-16 00:13:46 -0700 Created attachment 107614 modifed test case Attached the modifed test case . Just Added <!DOCTYPE html> to the actual test case. 468358 9 k_bolisetty 2011-09-16 00:17:27 -0700 http://www.w3.org/TR/html5-diff/#doctype In my opinion, the above link strengthens comments 5 & 7. As per the spec, browser need not render the page in standars mode unless <!DOCTYPE html> is mentioned. If I am correct, can some one move this to INVALID/WONTFIX state. 107614 2011-09-16 00:13:46 -0700 2011-09-16 00:13:46 -0700 modifed test case doctype.html text/html 533 k_bolisetty PCFET0NUWVBFIEhUTUw+CjxodG1sIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hodG1s Ij4KPGhlYWQ+Cjx0aXRsZT5TdHlsZXNoZWV0IGJ1ZzwvdGl0bGU+CjxzdHlsZT4KLm15VXBwZXJD YXNlQ2xhc3Mge2NvbG9yOiByZWR9Cjwvc3R5bGU+CjxzY3JpcHQ+CmZ1bmN0aW9uIHRlc3QoKSB7 CglhbGVydChkb2N1bWVudC5zdHlsZVNoZWV0c1swXS5jc3NSdWxlc1swXS5jc3NUZXh0KTsKfQo8 L3NjcmlwdD4KPC9oZWFkPgo8Ym9keT4KPGgxPkNzcyBydWxlIGxvd2VyY2FzZSBidWc8L2gxPgo8 b2w+Cgk8bGk+Q2xpY2sgdGhlIHRlc3QgYnV0dG9uIGJlbG93LjwvbGk+Cgk8bGk+T2JzZXJ2ZSB0 aGF0IHRoZSBjbGFzcyBuYW1lIGlzIGFsbCBsb3dlcmNhc2UgaW5zdGVhZCBvZiB0aGUgc3BlY2lm aWVkIGNhc2UgaW4gdGhlIENTUy48L2xpPgoJPGxpPkNvbXBhcmUgaXQgdG8gb3RoZXIgR2Vja28g b3IgT3BlcmEuPC9saT4KPC9vbD4KPGJ1dHRvbiBvbmNsaWNrPSJ0ZXN0KCkiPlRlc3Q8L2J1dHRv bj4KCjwvYm9keT4KPC9odG1sPgo=