[webkit-dev] Position on emerging standard: WebCodecs
Hello, I'm reaching out to see if WebKit would like to weigh in on the WebCodecs WICG proposal: https://discourse.wicg.io/t/webcodecs-proposal/3662. The WebCodecs API enables web developers to instantiate codecs (audio/video encoders/decoders) and use them to process individual frames. There is a related proposal for image decoders; it enables access to individual animation frames: https://discourse.wicg.io/t/proposal-imagedecoder-api-extension-for-webcodecs/4418. An implementation of these APIs is being developed in Chromium. Thank you, Dan Sanders ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Exposing FeaturePolicy to the web
Hi, WebKit currently implements the feature policy mechanism[1] to allow developers/sites to enabled/disable certain features and/or browser APIs like geolocation or access to camera among others. While implementing the WebXR API I realized that we are not exposing[2] the values of feature policies to the web. I was wondering whether that was made on purpouse (fingerprinting?, privacy?...) or it is just because the use cases were not considered relevant enough to implement it. I haven't found any bug tracking that. BR [1] https://w3c.github.io/webappsec-feature-policy [2] https://w3c.github.io/webappsec-feature-policy/#the-policy-object ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
