IDL generation in CSSOM for supported properties

[gsnedders]

CSSOM generates a variety of partial IDL fragments for each supported property, where:

The term supported CSS property refers to a CSS property that the user agent implements, including any vendor-prefixed properties, but excluding custom properties. A supported CSS property must be in its lowercase form for the purpose of comparisons in this specification.

A property name in CSS is a (CSS) ident token.

WebIDL attributes must be a (WebIDL) identifier.

Note that the CSS ident token is a superset of the WebIDL identifier.

What is the intended behaviour when there is a supported CSS property where the property name is an invalid WebIDL identifier?

(cc/ @tabatkins who may have opinions from the Syntax side)

[emilio]

Note that the WebIDL attributes aren't for the ident, but for the camel-cased version. This is supposed to create valid WebIDL attribute names, is there a case where it does not?

[gsnedders]

U+1000 is a valid CSS ident but not a valid WebIDL attribute name, for example.

[emilio]

Do we define any property with a non-ascii name? I don't think so, but ICBW.

[tabatkins]

We don't, and we have a CSSWG resolution to never use non-ASCII in language-defined constructs.

[gsnedders]

Should we add a specification conformance criteria to CSS Syntax forbidding non-ASCII?

[tabatkins]

I'm not opposed. ^_^