March 2021 - webkit-dev - lists.webkit.org

Updated Subversion installer for WebKit development on macOS
by Alexey Proskuryakov 31 Mar '21

31 Mar '21

Hi, We've posted a new svn installer for macOS to https://webkit.org/build-tools/ <https://webkit.org/build-tools/>. It now runs natively on Apple Silicon, and the build contains the fix for https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-17525 <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-17525>. Please let me know if anything doesn't work as expected. - Alexey

1 0

Request for position: Media Session video conferencing actions
by Tommy Steimel 30 Mar '21

30 Mar '21

Hi webkit-dev, This is a request for WebKit's position on adding video conferencing actions to the Media Session API spec. Note that this is the proposal that was discussed on the March 9th 2021 Media WG meeting. Spec change explainer: https://gist.github.com/steimelchrome/d52f0fb9a0a13c63a3cf2d4134b71682 Discussion (first comment is a copy of the explainer above): https://github.com/w3c/mediasession/issues/264 Summary: To make the Media Session API more useful for video conferencing websites, we'd like to add "togglemicrophone", "togglecamera", and "hangup" actions to the list of supported Media Session Actions. Thanks, Tommy

3 2

Request for Position on RTCRtpEncodingParameters.adaptivePtime
by Jakob Ivarsson 30 Mar '21

30 Mar '21

Hi webkit-dev, We would like to get an official position on the addition of adaptivePtime flag in RTCRtpEncodingParameters. Enabling the flag allows a sender to dynamically adjust the audio packet rate to better utilize the network link. Explainer: https://w3c.github.io/webrtc-extensions/explainer#a-new-flag-in-rtcrtpencod… Spec: https://w3c.github.io/webrtc-extensions/#dom-rtcrtpencodingparameters-adapt… The flag is currently available through an origin trial in Chrome ( https://chromestatus.com/feature/5752004691361792) // Jakob

2 1

Request for position on Handwriting Recognition API
by Jiewei Qian 29 Mar '21

29 Mar '21

Hi WebKit ! In Chrome, we've been prototyping a on-device handwriting recognition API. This API allows web developers to use advanced handwriting recognition technologies that are readily available on device, instead of integrating with third party (e.g. cloud) services. We'd like to get some feedback from WebKit developers. Chrome plans to run an experiment (origin trial) for this feature on Chrome OS from version 91 to 94. Thanks! Jiewei Relevant links: * Explainer: https://github.com/WICG/handwriting-recognition * TAG review: https://github.com/w3ctag/design-reviews/issues/591

1 0

WebKit SVN tree clousures (April 2021)
by Ling Ho 27 Mar '21

27 Mar '21

Hello WebKit, One of the infrastruture maintenance works that was planned for early March has been rescheduled for the weekend starting April 2nd. Our critical continuous integration services (EWS, post-commit bots, etc.) will be unavailable during: *Begin*: Friday, April 2nd, 2021. 5pm (PDT) *End*: Monday, April 5th, 2021. No later than 6pm (PDT) To avoid accumulating difficult to diagnose regressions during this lengthy outage, *WebKit SVN tree will be closed*. I will send out email if there is any change to the schedule. Please contact us at admin(a)webkit.org if you have any questions or concerns. Thank you, ... Ling Ho

1 0

Request for position: Support using WebOTP API in cross-origin iframes
by Yi Gu 26 Mar '21

26 Mar '21

Dear WebKit folks, We (Chromium) are adding support to use WebOTP API <http://web.dev/web-otp>in cross-origin iframes. As part of that we're interested in WebKit opinions around this API. In general WebKit and Chromium agree on the SMS format that is used in a SMS verification process. The specification <https://wicg.github.io/sms-one-time-codes> editors are from Apple and Google. On the format front, WebKit raised the initial request <https://github.com/WICG/sms-one-time-codes/issues/4> of using sms-one-time-code in nested frames to support third party or a separate service run by the same party. Cross-origin iframe support was included in the launch of the declarative API. <https://developer.apple.com/news/?id=z0i801mg> The difference is that Chromium uses this SMS format in an imperative API and that is WebOTP. WebKit's position in this API was "neutral" when we first launched it in M84. We'd like to get your fresh opinion around this API and the support in cross-origin iframes. Some useful links: Chrome Platform Status <https://www.chromestatus.com/feature/5679508336148480> Specification <https://wicg.github.io/web-otp/#sctn-permissions-policy> Design doc <https://docs.google.com/document/d/1dR-5-1O3SqAbQCRj_cBaQ7nQD5YlWzExcusmPcO…> TAG <https://github.com/w3ctag/design-reviews/issues/604> Cheers Yi

1 0

Request for position: Managed Configuration API
by Anatoliy Potapchuk 26 Mar '21

26 Mar '21

Hello webkit-dev, I'd like to request a position statement on the proposed Managed Configuration API <https://wicg.github.io/WebApiDevice/managed_config/>. This API allows administrators on managed devices to set up a JSON config that is accessible by the web site. On devices that are managed by an organization, there is a need to thoroughly set up the environment for the web applications before use. The configuration for each device may be not exactly the same, or even changes over time. What’s more important, the device administrator is not necessarily the owner of web applications they are using, which means that it’s impossible to set up everything on the web application side. Some real use cases are as follows. - Signage configuration: an enterprise application pulls the commercial content from the management console, then demonstrates it to the customers on in-store devices. - Personalization: an enterprise application pulls the application settings (i.e., single-touch or multi-touch on a tablet) from the management console preferred by administrators, then applies them to the local devices. Chrome Status Entry: https://chromestatus.com/feature/5755104466567168 Explainer: https://github.com/WICG/WebApiDevice/blob/main/Explainer.md Thank you for your consideration! Anatoliy

1 0

Request for position: WebAuthn support for credBlob and minimum PIN length
by Adam Langley 24 Mar '21

24 Mar '21

Dear WebKit folks, We (Chromium) are fleshing out our support for WebAuthn Level Two <https://www.w3.org/TR/webauthn/> and CTAP 2.1 <https://fidoalliance.org/specs/fido-v2.1-rd-20210309/fido-client-to-authent…> (the corresponding protocol between devices and security keys). As part of that we're interested in any WebKit opinions about the following: CTAP 2.1 credBlob extension <https://fidoalliance.org/specs/fido-v2.1-rd-20210309/fido-client-to-authent…> (Intent thread <https://groups.google.com/a/chromium.org/g/blink-dev/c/Vfg2o0peyYg/m/Vp0h8i…> , platform status entry <https://chromestatus.com/feature/5541178411843584> ): This is a bytestring stored by the authenticator, just like the user handle, but a separate value. Microsoft plan to use it in mixed web/native contexts to store the hash of some externally-provided information in order to authenticate it. (This only involves an IDL change in Chromium due to the way that we implemented authenticator extensions, it might not need code changes in WebKit.) Minimum PIN lengths <https://fidoalliance.org/specs/fido-v2.1-rd-20210309/fido-client-to-authent…> (not yet the subject of an Intent to Ship): This allows enterprises to configure a minimum PIN length greater than the default value of four. It also involves an extension <https://fidoalliance.org/specs/fido-v2.1-rd-20210309/fido-client-to-authent…> to report, to the enterprise, what minimum is in effect. The extension will involve IDL changes in Chromium for the same reason, and our PIN-related management UIs would have to be updated to respect the configured minimum. Cheers AGL

1 0

Caio Lima is now a WebKit reviewer
by Saam Barati 24 Mar '21

24 Mar '21

Hi folks, I'm happy to announce that Caio Lima is now a WebKit reviewer. Send your JavaScriptCore reviews his way! Congrats, Caio. - Saam

6 5

WebKit SVN tree clousures (March 2021)
by Ling Ho 22 Mar '21

22 Mar '21

Hello WebKit, Due to planned infrastructure maintenance, our critical continuous integration services (EWS and post-commit bots) will be unavailable during the following weekends: *Dates*: *Begin*: Friday, March 5th, 2021. 5pm (PST) *End*: Monday, March 8th, 2021. No later than 6pm (PST) *Begin*: Friday, March 19th, 2021. 5pm (PDT) *End*: Monday, March 22nd, 2021. No later than 6pm (PDT) To avoid accumulating difficult to diagnose regressions during this lengthy outage, *WebKit SVN tree will be closed*. Please email admin(a)webkit.org if you have any questions or concerns. Thanks, ... Ling Ho

2 3