W3C home > Mailing lists > Public > public-media-capture-logs@w3.org > August 2018

Re: [mediacapture-main] Origin isolation

From: Martin Thomson via GitHub <sysbot+gh@w3.org>
Date: Mon, 13 Aug 2018 01:14:39 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issue_comment.created-412385686-1534122878-sysbot+gh@w3.org>
Readable means that the contents (the frames of video, samples of audio) can be read somehow.  That might mean rendering to a canvas, web audio, or whatever other methods we provide for accessing content.

Copying doesn't imply a requirement that content be readable - we can create new tracks by cloning for instance, or we might copy the track to another origin (where it is probably equally unreadable), and we might consider rendering through a video tag as copying as well.

Yes, "rendered" means playback.  Just as we allow cross-origin images to be shown by a page, we can allow media to be played in the various ways we support (which includes capture of stills in canvas, which subsequently loses its origin-clean flag).

Size (meaning video width and height) is one property we might allow read access to along with frame rate and sample rate.  We might also permit reading of other metadata like field of view (if this is taken from a camera), the number of bits per sample, and other such things.  Enumerating those, or finding a set of rules that we might apply to the decision, would be good.

GitHub Notification of comment by martinthomson
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/529#issuecomment-412385686 using your GitHub account
Received on Monday, 13 August 2018 01:14:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:27:34 UTC