public-houdini-archive@w3.org from October 2016 by subject

[css-houdini-drafts] [css-paint-api] Add inputArguments to paint API

[css-houdini-drafts] [css-paint-api] algorithm for registering custom paint depends on undefined "constructor" variable

[css-houdini-drafts] [css-paint-api] class constructor valid flag is unused

[css-houdini-drafts] [css-paint-api] lack of complete examples is problematic

[css-houdini-drafts] [css-paint-api] scope of paint-valid flag being box (not box+use/size) seems wrong

[css-houdini-drafts] [css-paint-api] should normatively require switching between at least 2 worklet global scopes in most cases

[css-houdini-drafts] [css-paint-api] should paintWorker be a property on window (and thus be in the global namespace)?

[css-houdini-drafts] [css-properties-values-api] Substituting registered properties with var()

[css-houdini-drafts] [css-typed-om] .equals methods for CSSStyleValue subclasses

[css-houdini-drafts] [css-typed-om] CSSFontFaceValue.fontFaceName could be fontFamilyName?

[css-houdini-drafts] [typed-om] Shorter dimension constructors on the CSS namespace?

[css-houdini-drafts] [worklets] could the module responses cache and custom fetch steps be simplified?

[css-houdini-drafts] One repo per draft?

[css-houdini-drafts] Proposal, custom script based transitions

[css-houdini-drafts] Pull Request: Rename CSSFontFaceValue.fontFaceName to fontFamilyName

Closed: [css-houdini-drafts] Proposal, custom script based transitions

Last message date: Friday, 28 October 2016 22:45:07 UTC