Component Request: <Component_Name> |
||||||
Issue description1] Component Name: Blink>ImageCapture 2] Parent Component (e.g. Blink, UI>Browser, etc...): Blink 3] Description of Component: Capturing of Images on the Web, e.g. with a WebCam. 4] Admin/ Owner: mcasas@ 5] Please specify what triage practices will be followed for the component Weekly triaging done by owner and/or by other Web Platform team members.
,
Nov 22 2016
mcasas@: is this a valid bug?
,
Nov 22 2016
#2: yes, it's a valid bug and it belongs to Admin>ComponentRequest, so I shouldn't be the one assigned to it; forwarding to tkent@ who might know more about what to do here, and removing confusing component labels.
,
Nov 23 2016
I, as a Blink components expert, think it's ok to add it.
,
Nov 23 2016
There is a separate Blink>MediaStream>ImageCapture. What's the difference between that one and this one? It's confusing to have two components with the same name.
,
Nov 23 2016
#5: we talked about offline, let me post it here FTR. Also, blink>MediaStream>ImageCapture bugs will be moved to the new one and the former removed (deprecated). Rationale: - There are two Image capture APIs, one centralizes bugs under said Blink>MediaStream>... and the others, pertaining to <input capture> [1], are scattered. - Current ImageCapture component bugs are hanging from MediaStream due to Spec organization and do not reflect the user's view of the APIs, specially with the incoming polyfill [2] that bridges both APIs into one. [1] https://w3c.github.io/html-media-capture/ [2] https://github.com/GoogleChrome/imagecapture-polyfill
,
Nov 23 2016
Created Blink>ImageCapture, moved bugs there from Blink>MediaStream>ImageCapture and deleted old component. Please add an appropriate description and close the bug if everything looks good.
,
Nov 23 2016
#7 did the trick, closing, thanks! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by mcasas@chromium.org
, Nov 22 2016