October 2021 - webkit-dev - lists.webkit.org

Andres Gonzales is now a WebKit Reviewer
by Chris Fleizach 13 Oct '21

13 Oct '21

I'm happy to announce that Andres Gonzales is now a WebKit Reviewer! Congratulations Andres! 👍

1 0

GitHub Usernames in contributors.json
by Jonathan Bedard 08 Oct '21

08 Oct '21

Hello WebKittens, As I continue to bring up GitHub infrastructure, it’s coming time to start representing various permissions of the WebKit project in GitHub. In order to represent these permissions, we need a record of active contributor’s GitHub usernames. We’re doing this in contributors.json, which has now been moved to metadata/contributors.json. Adding GitHub users is supported as of 242713@main <https://commits.webkit.org/242713@main> (r283833 <https://trac.webkit.org/changeset/283833/webkit>). The expectation is that active contributors are adding their usernames to contributors.json over the next 4-6 weeks. A GitHub username in contributors.json will be necessary to retain committer and reviewer privileges as we transition to GitHub. Jonathan

1 0

Request for position: Digital Goods API
by Glen Robertson 08 Oct '21

08 Oct '21

Hi, I am requesting a standards position signal on the Digital Goods API. This is an API for querying and managing digital products to facilitate in-app purchases from web applications, in conjunction with the Payment Request API (which is used to make the actual purchases). The API would be linked to a digital distribution service connected to via the user agent. Explainer: https://github.com/WICG/digital-goods/blob/main/explainer.md Chromestatus: https://chromestatus.com/feature/5339955595313152 TAG review: https://github.com/w3ctag/design-reviews/issues/571 Let me know if you have any questions. Thanks -Glen Robertson (Chrome OS web apps platform team)

1 0

Request for position on Canvas 2D API extensions
by Fernando Serboncini 06 Oct '21

06 Oct '21

Specification Title: New Canvas 2D API Specification or proposal URL: explainers <https://github.com/fserb/canvas2d>, meta WhatWG bug <https://github.com/whatwg/html/issues/5613> WhatWG issues with PRs: - Canvas context loss <https://github.com/whatwg/html/issues/4809> - Conic gradient <https://github.com/whatwg/html/issues/5431> - willReadFrequently <https://github.com/whatwg/html/issues/5614> - Text modifiers <https://github.com/whatwg/html/issues/5617> - Reset function <https://github.com/whatwg/html/issues/5618> - RoundRect <https://github.com/whatwg/html/issues/5619> - Modern filters <https://github.com/whatwg/html/issues/5621> All the issues above have had some positive signal from WebKit prior to the PR submission.

1 0

Request for Position on Content Security Policy for dedicated workers
by Antonio Sartori 01 Oct '21

01 Oct '21

Hello Webkit-dev, I would like to ask for Webkit's official position on how Content Security Policy [1] for dedicated workers should be delivered. We have had to possibilities in the past: (a) Dedicated workers inherit the Content Security Policy from their owner context. (b) Dedicated workers use the policy delivered in their resource Content Security Policy HTTP response headers. The specced behaviour in CSP3 has initially been to do (a). However, Mozilla officially requested [2] to switch to (b) quite some time ago. The spec since then was refactored (inheritance and CSP initialization moved from CSP to html), and the specified behaviour is now (b) [3]. Chrome currently implements (a) while Firefox implements (b). We would like [4] to change chrome's behaviour to also adhere to the specified behaviour and implement (b). While from the few Web Platform Tests [5] we have in place I am guessing WebKit also implements (b), I would like to ask for an official position here. Thanks, Antonio [1] https://w3c.github.io/webappsec-csp/ [2] https://github.com/w3c/webappsec-csp/issues/336#issuecomment-423165240 [3] https://html.spec.whatwg.org/#initialize-worker-policy-container [4] https://chromestatus.com/feature/5715844005888000 [5] https://wpt.fyi/results/content-security-policy/inside-worker?label=experim…

1 0

Request for Position: MSE-for-WebCodecs
by Matt Wolenetz 01 Oct '21

01 Oct '21

Hi webkit-dev, This is a request for WebKit's position on the MSE-for-WebCodecs featgure: Explainer: https://github.com/wolenetz/mse-for-webcodecs/blob/main/explainer.md MSE spec issue tracking this feature: https://github.com/w3c/media-source/issues/184 ChromeStatus entry: https://www.chromestatus.com/feature/5649291471224832 Draft specification: https://github.com/w3c/media-source/pull/302 TAG review: https://github.com/w3ctag/design-reviews/issues/576 Please let us know if you have any feedback! Thanks, Matt

1 0