[css-properties-values-api] Reify specified values as CSSUnparsedValue
According to a recent spec change, the syntax of a registered custom property must be ignored until computed-value time. This means that we can unfortunately not reify specified values according to the syntax; instead all custom properties reify as CSSUnparsedValue, regardless of their registration status. This means that we can remove large parts of the Typed OM code which deals with PropertyRegistation for specified values and matching of incoming CSSStyleValues against registered syntax. The typedom.html test was also mostly re-written, as most of the things it tested are now not relevant anymore, or at least no longer as interesting as before. (The new reworked test basically verifies that registered custom properties behave as unregistered for attributeStyleMap and styleMap. For computedStyleMap, we should of course still reify according to the syntax). Bug: 641877 Change-Id: I4da7c25b8f066dd01388b6229bebe181513e9fd9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1713557 Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Reviewed-by:Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#680595}
Showing
This diff is collapsed.
This diff is collapsed.
Please register or sign in to comment