Add restrictions on 'clap' item property #188
Labels
Comments
aarongable
pushed a commit
to chromium/chromium
that referenced
this issue
Jun 9, 2023
Based on a revert of commit 6c184c0. Require the clean aperture to be anchored to (0, 0) to reduce privacy risks. See AOMediaCodec/av1-avif#188 and AOMediaCodec/av1-avif#189. Bug: 1167422 Change-Id: I92ffd82d10aeb1321565ed88d07500c74d381e76 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4585301 Commit-Queue: Wan-Teh Chang <[email protected]> Reviewed-by: Dale Curtis <[email protected]> Cr-Commit-Position: refs/heads/main@{#1155616}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Per the last meeting, the consensus was that we should add a restriction like the following on 'clap' to minimise the risk of it being misused:
The origin of the 'clap' item property shall be anchored to 0,0 (top-left) unless the full, un-cropped image item is included as a secondary item in an image collection.
This allows 'clap' to be used for dealing with HW limitations (since those typically only require padding along the right/bottom edge).
The exception also allows for more advanced camera features while making sure that users are not surprised about what is contained in the file.
The text was updated successfully, but these errors were encountered: