HTML5 device requirements going beyond support for a particular W3C spec

[jpiesing]

Back in July, in https://standards.cta.tech/apps/org/workgroup/hatf/download.php/18077/WAVE%20and%20HTML5-v3.pptx, I identified a number of subjects that people have found necessary to specify for devices supporting web video apps. These are as follows;

• Accuracy of value returned by HTMLMediaElement.currentTime
• Requirement to launch first page of Web App in full screen mode with no browser chrome
• Combinations of various W3C APIs - E.g. media fragment URLs with MSE
• MSE buffering and timing
• Root certificates for TLS
• Number of simultaneous HTTP connections & timing
• Size & persistence of cookies and data stored by web storage API
• URL length
• Graphics resolution used for rendering browser UI & relation to video resolution
• Still image formats
• Remote keys / key events
• Formatting of HTTP User Agent string
• Application loading & transition times
• Minimum graphics performance (decoding & rendering full screen images, CSS3 animations, etc)

I think (most of) these belong in the HTML5 API TF as they are specific to WAVE devices including the HTML5 environment.
IMHO the device playback specification is supposed to be also applicable to devices not including the HTML5 environment so (most of) these issues don't belong there.
However these also (IMHO) don't belong in an API list.
Also the reason others have found it necessary to write these down is to enable them to be tested. So they need to be written using "shall" and put in a document that is a specification & not guidelines.