[css-houdini-drafts] [css-typed-om] [css-paint-api] What happens to unsupported property names in the registered paint styleMap?

darrnshn has just created a new issue for https://github.com/w3c/css-houdini-drafts:

== [css-typed-om] [css-paint-api] What happens to unsupported property names in the registered paint styleMap? ==
Suppose we specify unsupported property names calling `registerPaint`:
```
registerPaint('bleh', class {
    static get inputProperties() {
        return [
            'invalid', // invalid CSS property
            'border', // shorthand
        ];
    }
    paint(ctx, geom, styleMap) {
        const properties = styleMap.getProperties().sort();
        console.log(properties); // ??
   }
});
```
The [paint spec says it's legal to have invalid properties](https://www.w3.org/TR/css-paint-api-1/#registering-custom-paint) in `inputProperties()` for forwards compat, but do these properties actually get returned by the style property map? Would the above output `[]` or `['invalid', 'border']`? Note that normally (using just the Typed OM API), a `StylePropertyMap` [can't contain unsupported property names](https://drafts.css-houdini.org/css-typed-om-1/#set-a-value-on-a-stylepropertymap).

Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/523 using your GitHub account

Received on Tuesday, 28 November 2017 23:35:20 UTC