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

The mst-content-hints are processing instructions from the JS application to the Web platform.
If an implementation  of the Web platform gets an arbitrary string, there are two possibilities:

- The implementation ignores the string. This seems harmless, but not useful.
- The implementation takes action on the string in a way that is not predictable to the application. This seems actively harmful to interoperability.

Thus, we decided to allow only setting values with a defined meaning (note that extensions to the spec may define more meanings).

Allowing only setting of values that have an interpretation by the platform allows feature detection on whether the platform supports that particular value.



-- 
GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/mst-content-hint/issues/47#issuecomment-678732736 using your GitHub account


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

Received on Sunday, 23 August 2020 05:46:54 UTC