This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24607 - <style type> should be ascii case-insensitive compare to "text/css". Similar to <script type>. http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2803
Summary: <style type> should be ascii case-insensitive compare to "text/css". Similar ...
Status: RESOLVED INVALID
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-10 20:11 UTC by contributor
Modified: 2014-02-20 12:11 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2014-02-10 20:11:00 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html
Multipage: http://www.whatwg.org/C#the-style-element
Complete: http://www.whatwg.org/c#the-style-element
Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/

Comment:
<style type> should be ascii case-insensitive compare to "text/css". Similar
to <script type>.
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2803

Posted from: 90.230.218.37 by simonp@opera.com
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.90 Safari/537.1
Comment 1 Ian 'Hixie' Hickson 2014-02-10 21:41:08 UTC 
I don't mind changing how <style type=""> works, but before I do so, we should make sure we agree on what the spec says already... as far as I can tell, <script type=""> doesn't work as you describe, at least not per spec. It's not just a string comparison. In particular, the spec says to do space trimming for <script type="">, then to compare the relevant component (i.e. not the parameters) to the strings given in the "scripting languages" section.
Comment 2 Simon Pieters 2014-02-11 09:56:05 UTC 
Ah, yeah I forgot <script type> trimmed whitespace. I meant that <style type> should be like <script type>.
Comment 3 Ian 'Hixie' Hickson 2014-02-11 19:52:06 UTC 
So, as far as I can tell, the spec matches at least Firefox, and is already consistent between <style type> and <script type>. Can you elaborate on what exactly you want and why?
Comment 4 Simon Pieters 2014-02-13 12:12:43 UTC 
I want to avoid MIME type parsing of <style type> because that seems like unnecessary complexity that <script type> doesn't have.
Comment 5 Ian 'Hixie' Hickson 2014-02-14 21:52:43 UTC 
But <script type> does have it.
Comment 6 Simon Pieters 2014-02-20 12:11:36 UTC 
Hmm. So long as the UA doesn't support a language *with* parameters, there's no difference. But if it does you need the MIME type parser. OK.