[css-typed-om] Possible inconsistency in errors thrown from `rectify a CSSColor* val`

[johannesodland]

There seems to be an inconsistency in the error thrown by the rectify a CSSColor* val procedures.
The specification specifies SyntaxError for some of the procedures, and TypeError for the angle procedure.
Web platform tests expect SyntaxError but Chrome seems to throw TypeError.

Should these be more consistent?

• rectify a CSSColorRGBComp val
  • Specified to throw a SyntaxError
  • WPT expects a SyntaxError
  • Chrome throws a TypeError (Tested through new CSSRGB(CSS.deg(5), 0, 0))
• rectify a CSSColorPercent val
  • Specified to throw a SyntaxError
  • WPT expects a SyntaxError
  • Chrome throws a TypeError (Tested through new CSSRGB(0, 0, 0, CSS.number(1)))
• rectify a CSSColorNumber val
  • Specified to throw a SyntaxError
  • Could not find WPT
  • Could not test in Chrome through CSSLab/CSSOKLab as they are not implemented
• rectify a CSSColorAngle val
  • Specified to throw a TypeError
  • cssHSL WPT expects a SyntaxError
  • cssHWB WPT expects both a TypeError and a SyntaxError depending on wether the input is a CSSNumericValue.
  • cssLCH WPT expects a SyntaxError
  • Chrome throws a Type error (tested through new CSSHSL(CSS.px(5), 0, 0))

[svgeesus]

@tabatkins

rectify a CSSColorAngle val

Looks like WPT should be updated for that one.

[svgeesus]

Could not test in Chrome through CSSLab/CSSOKLab as they are not implemented

Is there a bug for tracking that?

[johannesodland]

Could not test in Chrome through CSSLab/CSSOKLab as they are not implemented

Is there a bug for tracking that?

Couldn't find one, so created one here: https://issues.chromium.org/issues/428690993

[johannesodland]

Is there any reason that some of these procedures are specked to throw a SyntaxError and not a TypeError as in the Chrome implementation?