On Tue, Nov 15, 2022 at 7:23 PM Mike Taylor <[email protected]> wrote:
> On 11/15/22 11:21 AM, 'Christopher Cameron' via blink-dev wrote: > > *Contact email:* > [email protected] > > *Explainer:* None > *Specification:* None > > *Summary:* > These fields were accidentally exposed to the web in crrev.com/562990 by > way of crrev.com/427153. They are not part of any specification. > > These CLs landed in 2018 and 2016... do we have any UseCounter or usage > data? > We don't have usage counters for these members of ImageEncodeOptions. We do have stats for the relevant APIs though. The proposal (removing the parameters) will bring OffscreenCanvasConvertToBlob in line with the related CanvasToBlob and CanvasToDataURL, both of which are far more popular. - OffscreenCanvasConvertToBlob <https://chromestatus.com/metrics/feature/popularity#OffscreenCanvasConvertToBlob> is used by 0.0284% pageloads - CanvasToBlob <https://chromestatus.com/metrics/feature/popularity#CanvasToBlob> which is used by 0.1337% (leet?) of pageloads - CanvasToDataURL <https://chromestatus.com/metrics/feature/popularity#CanvasToDataURL> which is used by 19.1624% (wow!) of pageloads Of note is that: - There is no documentation of colorSpace and pixelFormat -- the only way to know they exist is to read our IDL files - The only effect that those ImageEncodeOptions can have is to degrade the quality of the resulting image -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGnfxj-1rrD9R2nwoqpSvN2gwONZ9_LdYFhz4TyjT5695wBx2Q%40mail.gmail.com.
