[css-paint-api] Remove alpha flag, in favour of a contextSettings flag?

[bfgeek]

Currently we have:

registerPaint('foo', class {
  static alpha = false;
});

Do we want this to be:

registerPaint('foo', class {
  static contextSettings = {
    alpha: false;
  };
});

This is to allow other context settings in the future in the same object, e.g. colorSpace.

[css-meeting-bot]

The CSS Working Group just discussed Remove alpha flag, in favour of a contextSettings flag?, and agreed to the following resolutions:

• RESOLVED: object called contextAttributes

The full IRC log of that discussion

<iank_> Topic: Remove alpha flag, in favour of a contextSettings flag?
<iank_> Github: https://github.com//issues/435
<fantasai> iank_: I noticed recently that the alpha flag is a little silly and not really future-proof
<fantasai> iank_: There's maybe some other arguments appearing here, e.g. color space
<fantasai> iank_: We don't want to keep on adding flags to the class, maybe makes sense to have a dictionary
<fantasai> franremy: Couldn't you just add on top of alpha? Why make the change?
<fantasai> iank_: Mirrors better the ???? API
<fantasai> s/????/getContext
<fantasai> iank_: However, I'm quite fine keeping the static ????
<fantasai> franremy: Not a preference, just wondering why changes
<fantasai> surma: I think mirroring getContext is a good idea. Also see getAlias call being useful here, so makes sense to add the objection
<fantasai> iank_: Do you have a better name than settings?
<fantasai> surma: options? :)
<fantasai> dino: We should reuse ... [looking stuff up]
<fantasai> iank_: canvasContextCreationAttributes?
<fantasai> dino: Yeah, contextCreationAttributes
<fantasai> dino: We know we're in a context, so creationAttributes
<fantasai> dino: But we know its attributes so maybe just creation
<fantasai> dino: I don't think we should use the word settings
<fantasai> dino: creationAttributions
<fantasai> TabAtkins: Can you make it longer, please?
<fantasai> Rossen: canvasContextCreationAttributes
<fantasai> TabAtkins: Yup, thanks
<fantasai> iank_: Let's do a twitter poll, and pick the most popular
<fantasai> surma: Just use contextAttributes. That's how MDN lists it for getAttribute2D
<fantasai> Rossen: Sounds like we're going with the boject, calling it contextAttributes
<fantasai> Rossen: which is nicely in MDN already
<fantasai> Rossen: Opinions or objections?
<fantasai> RESOLVED: object called contextAttributes

[domenic]

Why attributes? We already have enough things on the platform called attributes (IDL and content attributes). With my web dev hat on I'd pick "options".

[bfgeek]

This has been fixed, and is now contextOptions.