public-houdini-archive@w3.org from February 2018 by subject

[css-houdini-drafts] [css-paint-api] Cannot get custom properties defined in body element

[css-houdini-drafts] [css-properties-values-api] named parameters in custom values

[css-houdini-drafts] [css-typed-om-1] "equal numeric values" algorithm is possibly problematic

[css-houdini-drafts] [css-typed-om-1] "equal numeric values" may return false when people might expect true

[css-houdini-drafts] [css-typed-om-1] "invert" should be clear about what it means by "inverse"

[css-houdini-drafts] [css-typed-om-1] "negate" needs to say what global it's creating things in

[css-houdini-drafts] [css-typed-om-1] "rectify a numberish value" doesn't define the global it creates the CSSUnitValue in

[css-houdini-drafts] [css-typed-om-1] Behavior of indexed setter on CSSUnparsedValue is not defined.

[css-houdini-drafts] [css-typed-om-1] CSSUnparsedValue's "variable" getter needs to be defined.

[css-houdini-drafts] [css-typed-om-1] CSSUnparsedValue's length could be defined more clearly

[css-houdini-drafts] [css-typed-om-1] CSSVariableReferenceValue's "variable" getter needs to be defined.

[css-houdini-drafts] [css-typed-om-1] Does computedStyleMap() always return a new object?

[css-houdini-drafts] [css-typed-om-1] Duplicating a CSSVariableReferenceValue is harder than it probably should be

[css-houdini-drafts] [css-typed-om-1] Exposed value for partial interface Element makes no sense and is not valid Web IDL

[css-houdini-drafts] [css-typed-om-1] Exposed value for partial interface Element makes no sense.

[css-houdini-drafts] [css-typed-om-1] How does StylePropertyMap interact with CSSStyleDeclaration?

[css-houdini-drafts] [css-typed-om-1] Is it intentional that only existing items in a CSSUnparsedValue can be mutated?

[css-houdini-drafts] [css-typed-om-1] liveness behavior not very clear for the set of properties on StylePropertyMaps

[css-houdini-drafts] [css-typed-om-1] rectify a keywordish value allows creation of empty-string CSSKeywordValues

[css-houdini-drafts] [css-typed-om-1] rectify a keywordish value doesn't define the global it creates the CSSKeywordValue in

[css-houdini-drafts] [css-typed-om-1] Should "negate" handle a CSSMathSum of CSSMathNegates?

[css-houdini-drafts] [css-typed-om-1] Should probably be more explicit about 0 handling in "invert"

[css-houdini-drafts] [css-typed-om-1] What does computedStyleMap() do on elements that are in documents with no browsing context?

[css-houdini-drafts] [css-typed-om-1] Why is the new thing on ElementCSSInlineStyle called attributeStyleMap, not styleMap

[css-houdini-drafts] [css-typed-om-1]"contains" link in "delete" section is broken

[css-houdini-drafts] [css-typed-om-1]"Throw a TypeError and exit this algorithm" wording is weird

[css-houdini-drafts] [css-typed-om-1]has() behavior for StylePropertyMap undefined

[css-houdini-drafts] [css-typed-om-1]Likely typo in prose for StylePropertyMapReadOnly

[css-houdini-drafts] [css-typed-om-1]Manual definition of the map entries for StylePropertyMapReadOnly contradicts Web IDL

[css-houdini-drafts] [css-typed-om-1]Probably need to define the order of additions in add() step 3

[css-houdini-drafts] [css-typed-om-1]Probably need to define the order of multiplications in mul() step 3

[css-houdini-drafts] [css-typed-om-1]Probably need to define the order of multiplications in mul() step 3 and step 4

[css-houdini-drafts] [css-typed-om-1]The IDL for StylePropertyMap is not valid due to multiple maplike declarations

[css-houdini-drafts] [css-typed-om-1]The IDL for StylePropertyMapReadOnly has an invalid "get" method

[css-houdini-drafts] [css-typed-om-1]The IDL for StylePropertyMapReadOnly has an invalid "has" method

[css-houdini-drafts] [css-typed-om-1]update() behaves a bit oddly for non-single-valued properties

[css-houdini-drafts] [css-typed-om] "get all values from a StylePropertyMap" assumes underlying model might not be list

[css-houdini-drafts] [css-typed-om] Add pseudoElt argument to computedStyleMap(), or wait for PseudoElement interface?

[css-houdini-drafts] [css-typed-om] computedStyleMap()

[css-houdini-drafts] [css-typed-om] CSSImageValue should specify units of intrinsicWidth and intrinsicHeight

[css-houdini-drafts] [css-typed-om] CSSStyleValue normalization

[css-houdini-drafts] [css-typed-om] CSSURLImageValue

[css-houdini-drafts] [css-typed-om] CSSURLImageValue constructor probably shouldn't require "url()" around the URL

[css-houdini-drafts] [css-typed-om] CSSURLImageValue url setter should be specified

[css-houdini-drafts] [css-typed-om] Describe how the StylePropertyMaps should interact with custom properties

[css-houdini-drafts] [css-typed-om] Do we need an updateAll() method that gets and sets a list?

[css-houdini-drafts] [css-typed-om] Does the is2D design allow for inconsistent interpretation of CSSTransformComponents?

[css-houdini-drafts] [css-typed-om] Editorial: "If value is an empty string throw"

[css-houdini-drafts] [css-typed-om] If parseMultiple is true, but property is a single-valued property

[css-houdini-drafts] [css-typed-om] Let props be the value of this’s [[declarations]] internal slot internal slot

[css-houdini-drafts] [css-typed-om] Link "CSS Values"

[css-houdini-drafts] [css-typed-om] make green block under "subdivide into iterations" red

[css-houdini-drafts] [css-typed-om] Missing spec definition for CSSTransformValue.set

[css-houdini-drafts] [css-typed-om] need to specify mappings between syntax, typed OM object tree, and underlying representation

[css-houdini-drafts] [css-typed-om] parse a CSSStyleValue: let usage

[css-houdini-drafts] [css-typed-om] Question about computed values

[css-houdini-drafts] [css-typed-om] references to the "match" definition should link to it

[css-houdini-drafts] [css-typed-om] Reifying text-decoration-line

[css-houdini-drafts] [css-typed-om] rule on inferring <length-percentage> is too vague

[css-houdini-drafts] [css-typed-om] Serialization of CSSStyleValues constructed from string

[css-houdini-drafts] [css-typed-om] Setting list-valued properties to var() refs.

[css-houdini-drafts] [css-typed-om] Shorthands in StylePropertyMap

[css-houdini-drafts] [css-typed-om] Should StylePropertyMapReadonly.size be unsigned long?

[css-houdini-drafts] [css-typed-om] Significance of maplike in StylePropertyMap

[css-houdini-drafts] [css-typed-om] spec should clarify inheritance of CSSImageValue from CSSResourceValue for non-network image types

[css-houdini-drafts] [css-typed-om] Spec up ColorValue

[css-houdini-drafts] [css-typed-om] specify CSSMatrixComponentOptions default with IDL defaults?

[css-houdini-drafts] [css-typed-om] Stringification behavior

[css-houdini-drafts] [css-typed-om] StylePropertyMap order

[css-houdini-drafts] [css-typed-om] Transform serialization wording should be rephrased

[css-houdini-drafts] [css-typed-om] Unclear how parse a CSSStyleValue returns CSSStyleValue objects

[css-houdini-drafts] [css-typed-om] Unsupported color values

[css-houdini-drafts] [css-typed-om] What do numeric font weights reify to?

[css-houdini-drafts] [css-typed-om] What does lack of range restriction imply about serialization?

[css-houdini-drafts] [css-typed-om]Define precisely which properties are list-valued and which aren't, probably in an appendix.

[css-houdini-drafts] [typed-om] Trim CSSResourceValue and subclasses to opaque objects for this level, punt rest to level 2

[css-houdini-drafts] Add clarification about custom properties in StylePropertyMaps

[css-houdini-drafts] Add CSSMathValue Serialization body

[css-houdini-drafts] Add full table of properties and what CSSStyleValues types they normalize to

[css-houdini-drafts] Clarify CSSNumericValues.equals

[css-houdini-drafts] Clarify CSSUnparsedValue and CSSVariableReferenceValue.

[css-houdini-drafts] Clarify CSSURLImageValue.url

[css-houdini-drafts] computedStyleMap() must return same object

[css-houdini-drafts] Create EXPLAINER.md first draft

[css-houdini-drafts] CSSImageValue intrinsicWidth/Height should be unsigned long

[css-houdini-drafts] CSSImageValue ratio

[css-houdini-drafts] CSSImageValue ratio and no-cors fetches

[css-houdini-drafts] CSSPositionValue definition should state rules for mapping syntax to objects

[css-houdini-drafts] CSSStyleValue static methods do not return anything

[css-houdini-drafts] CSSURLImageValue url internal slot links to url IDL attribute

[css-houdini-drafts] Editorial: "initially be"

[css-houdini-drafts] Example 7 should be polling `computedStyleMap()` not attributeStyleMap

[css-houdini-drafts] Extend match concept to other style values

[css-houdini-drafts] Gather and publish CSS Typed OM performance data in an explainer?

[css-houdini-drafts] Pull Request: Add a few examples to the reification table

[css-houdini-drafts] Pull Request: Add description of CSSURLImageValue getter

[css-houdini-drafts] Pull Request: Add match references

[css-houdini-drafts] Pull Request: Add spec text for CSSTransformValue.set

[css-houdini-drafts] Pull Request: Add table of what popular properties normalize to

[css-houdini-drafts] Pull Request: Add units of `CSSImageValue`.intrinsic{Width, Height}

[css-houdini-drafts] Pull Request: Be more explicit about throwing RangeError in CSSMathValue.invert()

[css-houdini-drafts] Pull Request: Clarify CSSUnparsedValue and CSSVariableReferenceValue.

[css-houdini-drafts] Pull Request: Clarify CSSURLImageValue.url

[css-houdini-drafts] Pull Request: Clarify inverse to be multiplicative inverse.

[css-houdini-drafts] Pull Request: computedStyleMap() must return same object

[css-houdini-drafts] Pull Request: Create EXPLAINER.md first draft

[css-houdini-drafts] Pull Request: Enforce ordering on order of operations

[css-houdini-drafts] Pull Request: Example 7 - queries computedStyleMap() instead of specified attributeStyleMap

[css-houdini-drafts] Pull Request: Extend match concept to other style values

[css-houdini-drafts] Pull Request: File issues for remaining issues in Typed OM

[css-houdini-drafts] Pull Request: Format table of CSS Properties to StyleValues normalization

[css-houdini-drafts] Pull Request: Move comment about resources that don't need network request

[css-houdini-drafts] Pull Request: Reference CSSPositionValue normalization where relevant

[css-houdini-drafts] Pull Request: Remove redundant reference to exit this algorithm

[css-houdini-drafts] Pull Request: Remove references to CSSKeywordish

[css-houdini-drafts] Pull Request: Remove StylePropertyMap.update()

[css-houdini-drafts] Pull Request: Revert back to no defaults for CSSMatrixComponentOptions.is2D

[css-houdini-drafts] Pull Request: Serialize out of range values as calcs

[css-houdini-drafts] Remove StylePropertyMap.update()

[css-houdini-drafts] Restrict workers that `CSSStyleValue` is exposed to

[css-houdini-drafts] Serialization from CSSOM Values

[css-houdini-drafts] Serialize out of range values as calcs

[css-houdini-drafts] Should we be using DOMString, USVString, or CSSOMString?

[css-houdini-drafts] The IDL for StylePropertyMap is not valid

[css-houdini-drafts] Unclear how parse a CSSStyleValue returns CSSStyleValue objects

[css-houdini-drafts] Use defaults for CSSMatrixComponentOptions

[css-houdini-drafts] Why are these exposed in Workers?

Closed: [css-houdini-drafts] [css-typed-om-1] "equal numeric values" algorithm is possibly problematic

Closed: [css-houdini-drafts] [css-typed-om-1] "equal numeric values" may return false when people might expect true

Closed: [css-houdini-drafts] [css-typed-om-1] "invert" should be clear about what it means by "inverse"

Closed: [css-houdini-drafts] [css-typed-om-1] Behavior of indexed setter on CSSUnparsedValue is not defined.

Closed: [css-houdini-drafts] [css-typed-om-1] CSSUnparsedValue's length could be defined more clearly

Closed: [css-houdini-drafts] [css-typed-om-1] CSSVariableReferenceValue's "variable" getter needs to be defined.

Closed: [css-houdini-drafts] [css-typed-om-1] Does computedStyleMap() always return a new object?

Closed: [css-houdini-drafts] [css-typed-om-1] Duplicating a CSSVariableReferenceValue is harder than it probably should be

Closed: [css-houdini-drafts] [css-typed-om-1] Exposed value for partial interface Element makes no sense and is not valid Web IDL

Closed: [css-houdini-drafts] [css-typed-om-1] Is it intentional that only existing items in a CSSUnparsedValue can be mutated?

Closed: [css-houdini-drafts] [css-typed-om-1] rectify a keywordish value allows creation of empty-string CSSKeywordValues

Closed: [css-houdini-drafts] [css-typed-om-1] rectify a keywordish value doesn't define the global it creates the CSSKeywordValue in

Closed: [css-houdini-drafts] [css-typed-om-1] Should "negate" handle a CSSMathSum of CSSMathNegates?

Closed: [css-houdini-drafts] [css-typed-om-1] Should probably be more explicit about 0 handling in "invert"

Closed: [css-houdini-drafts] [css-typed-om-1] Why is the new thing on ElementCSSInlineStyle called attributeStyleMap, not styleMap

Closed: [css-houdini-drafts] [css-typed-om-1]"contains" link in "delete" section is broken

Closed: [css-houdini-drafts] [css-typed-om-1]"Throw a TypeError and exit this algorithm" wording is weird

Closed: [css-houdini-drafts] [css-typed-om-1]has() behavior for StylePropertyMap undefined

Closed: [css-houdini-drafts] [css-typed-om-1]Likely typo in prose for StylePropertyMapReadOnly

Closed: [css-houdini-drafts] [css-typed-om-1]Manual definition of the map entries for StylePropertyMapReadOnly contradicts Web IDL

Closed: [css-houdini-drafts] [css-typed-om-1]Probably need to define the order of additions in add() step 3

Closed: [css-houdini-drafts] [css-typed-om-1]Probably need to define the order of multiplications in mul() step 3 and step 4

Closed: [css-houdini-drafts] [css-typed-om-1]The IDL for StylePropertyMap is not valid due to multiple maplike declarations

Closed: [css-houdini-drafts] [css-typed-om-1]The IDL for StylePropertyMapReadOnly has an invalid "get" method

Closed: [css-houdini-drafts] [css-typed-om-1]The IDL for StylePropertyMapReadOnly has an invalid "has" method

Closed: [css-houdini-drafts] [css-typed-om-1]update() behaves a bit oddly for non-single-valued properties

Closed: [css-houdini-drafts] [css-typed-om] Add pseudoElt argument to computedStyleMap(), or wait for PseudoElement interface?

Closed: [css-houdini-drafts] [css-typed-om] algorithm for coercing value doesn't describe how to check grammar

Closed: [css-houdini-drafts] [css-typed-om] CSSImageValue should specify units of intrinsicWidth and intrinsicHeight

Closed: [css-houdini-drafts] [css-typed-om] CSSStyleValue normalization

Closed: [css-houdini-drafts] [css-typed-om] CSSStyleValue static methods do not return anything

Closed: [css-houdini-drafts] [css-typed-om] CSSURLImageValue constructor probably shouldn't require "url()" around the URL

Closed: [css-houdini-drafts] [css-typed-om] CSSURLImageValue url setter should be specified

Closed: [css-houdini-drafts] [css-typed-om] definition of CSSMathValue.equals() should be a little clearer

Closed: [css-houdini-drafts] [css-typed-om] Describe how the StylePropertyMaps should interact with custom properties

Closed: [css-houdini-drafts] [css-typed-om] Do we need an updateAll() method that gets and sets a list?

Closed: [css-houdini-drafts] [css-typed-om] Does the is2D design allow for inconsistent interpretation of CSSTransformComponents?

Closed: [css-houdini-drafts] [css-typed-om] Editorial: "If value is an empty string throw"

Closed: [css-houdini-drafts] [css-typed-om] If parseMultiple is true, but property is a single-valued property

Closed: [css-houdini-drafts] [css-typed-om] Let props be the value of this’s [[declarations]] internal slot internal slot

Closed: [css-houdini-drafts] [css-typed-om] Link "CSS Values"

Closed: [css-houdini-drafts] [css-typed-om] make green block under "subdivide into iterations" red

Closed: [css-houdini-drafts] [css-typed-om] Missing spec definition for CSSTransformValue.set

Closed: [css-houdini-drafts] [css-typed-om] parse a CSSStyleValue: let usage

Closed: [css-houdini-drafts] [css-typed-om] Question about computed values

Closed: [css-houdini-drafts] [css-typed-om] references to the "match" definition should link to it

Closed: [css-houdini-drafts] [css-typed-om] Reifying text-decoration-line

Closed: [css-houdini-drafts] [css-typed-om] rule on inferring <length-percentage> is too vague

Closed: [css-houdini-drafts] [css-typed-om] Setting list-valued properties to var() refs.

Closed: [css-houdini-drafts] [css-typed-om] Should StylePropertyMapReadonly.size be unsigned long?

Closed: [css-houdini-drafts] [css-typed-om] Significance of maplike in StylePropertyMap

Closed: [css-houdini-drafts] [css-typed-om] spec should clarify inheritance of CSSImageValue from CSSResourceValue for non-network image types

Closed: [css-houdini-drafts] [css-typed-om] StylePropertyMap order

Closed: [css-houdini-drafts] [css-typed-om] Transform serialization wording should be rephrased

Closed: [css-houdini-drafts] [css-typed-om] Unclear how parse a CSSStyleValue returns CSSStyleValue objects

Closed: [css-houdini-drafts] [css-typed-om] Unsupported color values

Closed: [css-houdini-drafts] [css-typed-om] What do numeric font weights reify to?

Closed: [css-houdini-drafts] [typed-om] Trim CSSResourceValue and subclasses to opaque objects for this level, punt rest to level 2

Closed: [css-houdini-drafts] Add full table of properties and what CSSStyleValues types they normalize to

Closed: [css-houdini-drafts] CSSPositionValue definition should state rules for mapping syntax to objects

Closed: [css-houdini-drafts] Editorial: "initially be"

Closed: [css-houdini-drafts] Example 7 should be polling `computedStyleMap()` not attributeStyleMap

Closed: [css-houdini-drafts] Gather and publish CSS Typed OM performance data in an explainer?

Closed: [css-houdini-drafts] Restrict workers that `CSSStyleValue` is exposed to

Closed: [css-houdini-drafts] Should we be using DOMString, USVString, or CSSOMString?

Closed: [css-houdini-drafts] Why are these exposed in Workers?

Last message date: Wednesday, 28 February 2018 22:26:45 UTC