[mst-content-hint] Why are arbitrary values disallowed for hints? (#47)

kenchris has just created a new issue for https://github.com/w3c/mst-content-hint:

== Why are arbitrary values disallowed for hints? ==
In reference to https://github.com/w3ctag/design-reviews/issues/539

Why are arbitrary values (anything aside from well-known values or "", since on the surface it is a DOMString property) disallowed for hints? (Wasn't quite clear from the spec; is it because internally [e.g. during transport] these values are encoded into enums?)

Please view or discuss this issue at https://github.com/w3c/mst-content-hint/issues/47 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 19 August 2020 20:22:33 UTC