Re: [w3ctag/design-reviews] Region Capture (Issue #710)

> First of all, this looks pretty useful.

Thanks. :-)

> API surface-wise, what happens when one tries to create a crop target on a element that is not attached to a document, hence not visible? (I assume it can be rendered and therefore can be captured, but seems like a bug or an interesting side-effect feature?)

The thing that happens if one creates a CropTarget for an element that is attached, but then detaches the element. Namely, the track is muted¹.

> Initially we thought this was replicating what native does and provides a bounding box to be streamed, but that does not seem to be the case here.

I think you initial interpretation **was** in fact correct. The element defines a bounding box to be streamed.

> This feels like a user expectation that should be fulfilled.

The user is not in control of the feature; the application is. The application could be saving the cropped file to disk, storing it remotely, doing OCR inside of it... Anything, really. Whether it's user-facing or not is up to the application, and not up to the API.

> We weren't able to figure out the user flow of how the preview is presented the user in the example code.

Could you please clarify the question? What preview are you asking about? (Note clarification above.)

--
[1] The muting part is currently under discussion. It's unclear at the moment if we'll set [MediaStreamTrack.muted](https://developer.mozilla.org/en-US/docs/Web/API/MediaStreamTrack/muted), but regardless, no frames will be delivered, so "effectively muted."

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/710#issuecomment-1032420051

You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/710/1032420051@github.com>