You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Small point that came up in the TAG Review, the ScrollTimeline interface is currently using DOMString to represent keyword and length/percentage values. This should use the appropriate CSS Typed OM classes instead.
Using strings for CSS values is a historical artifact we're trying to eliminate, new APIs shouldn't use them.
The text was updated successfully, but these errors were encountered:
Thanks. This has been something that was suggested before as well by @andruud in #4352 as well.
Given TAG's recommendation here we should go ahead and make this change. I also like Tab's suggestion to treat strings implicitly as keyword.
Use appropriate CSSTypedOM instead of DOMStrings in the API. Fixes#5213.
Changes:
- For offsets use `CSSNumericValue` or `CSSKeywordish` instead of DOMString
- When setting the offset, the grammars for these values is check to ensure only the valid subset can be set.
- When computing effective scroll offset check the offset actual type and interpret it accordingly
- Update examples to showcase the API and add noted to clarify the usage.
Small point that came up in the TAG Review, the ScrollTimeline interface is currently using DOMString to represent keyword and length/percentage values. This should use the appropriate CSS Typed OM classes instead.
Using strings for CSS values is a historical artifact we're trying to eliminate, new APIs shouldn't use them.
The text was updated successfully, but these errors were encountered: