Re: [css-houdini-drafts] [css-typed-om] Should StyleMap be case sensitive?

The CSS Working Group just discussed `https://github.com/w3c/css-houdini-drafts/issues/309`, and agreed to the following resolutions:

* `RESOLVED: StyleMap for CSS properties is ASCII case-insensitive because that's how CSS property names are defined`

<details><summary>The full IRC log of that discussion</summary>
&lt;nainar> Topic: https://github.com/w3c/css-houdini-drafts/issues/309<br>
&lt;fantasai> GitHub: https://github.com/w3c/css-houdini-drafts/issues/309<br>
&lt;fantasai> TabAtkins: Should the StyleMap be case sensitive for property names?<br>
&lt;fantasai> TabAtkins: .style isn't<br>
&lt;fantasai> TabAtkins: It doesn't care about casing<br>
&lt;fantasai> TabAtkins: We do not care which way it goes, it's trivial<br>
&lt;fantasai> TabAtkins: So asking for opinions<br>
&lt;fantasai> fantasai: What does it even mean for it to be case-sensitive?<br>
&lt;fantasai> TabAtkins: Only accepts lower case<br>
&lt;fantasai> dbaron: Is it clear that the canonical case for CSS is lower-case?<br>
&lt;fantasai> ...<br>
&lt;fantasai> ?: Interaction with custom properties?<br>
&lt;fantasai> TabAtkins: Custom properties are always case-sensitive<br>
&lt;surma> s/?/surma<br>
&lt;fantasai> fantasai: I'll settle this for you, I'll object to treating CSS properties as case-sensitive.<br>
&lt;fantasai> dbaron: I think it would be really weird for this to be case-sensitive<br>
&lt;fantasai> dbaron: Don't want TypedOM to be different from other OM<br>
&lt;dbaron> dbaron: people sometimes pass properties to functions<br>
&lt;fantasai> RESOLVED: StyleMap for CSS properties is ASCII case-insensitive because that's how CSS property names are defined<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/309#issuecomment-319314249 using your GitHub account

Received on Tuesday, 1 August 2017 09:09:48 UTC