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
These comments were originally filed by @npdoty in response to a wide review request on HTML5.3, and logged as issue w3c/html#1457. They relate specifically to the HTML Media Capture specification, rather than to HTML.
There are some nice privacy advantages to using this model of user-directed input for camera access and it's nice to see that reflected in the HTML spec.
...
The Media Capture spec's Security and privacy considerations section is non-normative; it explicitly doesn't add those as normative requirements on the
UA. Perhaps it should; the advice about stripping invisible, sensitive metadata (the example is EXIF data, which might include geolocation) seems especially
important.
There are privacy implications to other requirements in that spec. For example, the UA is forbidden from saving captured media to storage, which seems
like a privacy advantage, although I could imagine some abuse or violation of user preferences from that requirement.>
The text was updated successfully, but these errors were encountered:
These comments were originally filed by @npdoty in response to a wide review request on HTML5.3, and logged as issue w3c/html#1457. They relate specifically to the HTML Media Capture specification, rather than to HTML.
...
The Media Capture spec's Security and privacy considerations section is non-normative; it explicitly doesn't add those as normative requirements on the
UA. Perhaps it should; the advice about stripping invisible, sensitive metadata (the example is EXIF data, which might include geolocation) seems especially
important.
There are privacy implications to other requirements in that spec. For example, the UA is forbidden from saving captured media to storage, which seems
like a privacy advantage, although I could imagine some abuse or violation of user preferences from that requirement.>
The text was updated successfully, but these errors were encountered: