mediacapture-region
mediacapture-region copied to clipboard
Clarify the cropTarget minting processing model
Fixes #48 [edit jib]. This is to help move along the discussion at https://github.com/w3c/mediacapture-region/issues/17 and to make the processing model better reflect the intended Chromium implementation.
This PR improves the quality of the document without diverging from the status quo. If I'm wrong about it - if there was a delta vis-à-vis the status quo - please point it out and it can be corrected. Otherwise, let's please merge this PR. @jan-ivar, @youennf
I'd like to help push this PR towards being approved and merged in today's editors' meeting. Is anything else requested here, @jan-ivar / @youennf?
Since this PR hasn't been split up as requested, it still contains items under discussion in #48, so I've marked it as "Fixes #48" in the OP, to help make that clear.
It is not ready to be merged in an Editor's Meeting. #48 is set to be discussed at our next interim as part of #17.
Is the problem with this PR solely that it introduces the affordance that CropTarget-minting may fail? Or do you have other issues with it? Assuming that's the only issue - if we remove that part, and leave a note explaining that there's a debate over this issue, would that work for you, and allow consensus to emerge for this PR?
I'm opposed to a note. Issues are covered on github and we're discussing #48 next week.