May 2022 - webkit-dev - lists.webkit.org

Request for position: Fullscreen Companion Window
by Ben Morss 09 May '22

09 May '22

Hi all, We'd like to get WebKit's position on a proposed enhancement to the new Multi-Screen Window Placement API. We propose to create an affordance allowing a site to to place fullscreen content and a popup window on separate screens from a single user activation. For more details, please see these links: - Explainer: https://docs.google.com/document/d/1RRlGQharWVnmxKTomfKhNiaeE31L7iXHeXVfifO… - Original API specification: https://w3c.github.io/window-placement/ - Original API Draft Community Group Report: https://webscreens.github.io/window-placement/ Thanks for your feedback on this! All best, Ben

1 0

Request for position: Opaque Response Blocking (ORB, aka CORB++)
by Łukasz Anforowicz 09 May '22

09 May '22

Hello webkit-dev@, Can you please provide an official WebKit position on Opaque Response Blocking (ORB, aka CORB++)? ORB spec has been iterated on at https://github.com/annevk/orb and both Firefox and Chrome are actively working on implementing it (Chrome intends to ship ORB v0.1 in M103 <https://groups.google.com/a/chromium.org/g/blink-dev/c/ScjhKz3Z6U4/m/5i_0V7…>). In the past WebKit focused on CORP <https://github.com/whatwg/fetch/issues/687> (and COOP/COEP), but there was some recent interest in implementing CORB and/or ORB in WebKit <https://lists.webkit.org/pipermail/webkit-dev/2022-April/032172.html>. Given above, how can the ORB entry at https://chromestatus.com/feature/4933785622675456 describe Safari view on ORB? Positive? Neutral? Negative? Leave at "no signal"? -- Thanks, Lukasz

1 0

Request for position: Capability Delegation
by Mustaq Ahmed 09 May '22

09 May '22

Hi webkit-dev: This is a request for WebKit's position on Capability Delegation. Capability Delegation defines a mechanism through which a script can delegate its ability to call a restricted API to another browsing context it trusts. This is a generic mechanism, and Chrome is currently looking into supporting two capabilities (Payment-Request and Fullscreen) in a cross-origin iframe through this generic mechanism. See more details in the explainer <https://github.com/WICG/capability-delegation/>. - Proposed spec <https://wicg.github.io/capability-delegation/spec.html> - WICG issue tracker <https://github.com/WICG/capability-delegation/issues> - Chrome-status entries for Payment Request <https://www.chromestatus.com/feature/5708770829139968> and Fullscreen <https://chromestatus.com/feature/6441688242323456>. Thanks. Mustaq Google Chrome

1 0

Introduction.md: JS wrapper & Node lifecycle management
by Ryosuke Niwa 07 May '22

07 May '22

Hi all, I've recently written up an overview of how the lifecycle of JS wrappers <https://github.com/WebKit/WebKit/blob/main/Introduction.md#js-wrapper-lifec…> and DOM nodes <https://github.com/WebKit/WebKit/blob/main/Introduction.md#referencing-coun…> are managed in WebKit in Introduction.md <https://github.com/WebKit/WebKit/blob/main/Introduction.md>. I'd recommend glancing over it even if you're an experienced WebKit contributor since I've seen so many patches that have obvious bugs in these two areas over the years. Also, let me know if you think of anything we should add or clarify in these two sections of Introduction.md. - R. Niwa

1 1

Request for Position: Element.isVisible method
by Joey Arhar 05 May '22

05 May '22

Hello WebKit devs, I am implementing the Element.isVisible method in Chromium, and I would like to hear WebKit's position on the feature. Chromestatus entry: https://chromestatus.com/feature/5163102852087808 Spec: https://drafts.csswg.org/cssom-view/#dom-element-isvisible Explainer: https://github.com/WICG/display-locking/blob/main/explainers/isvisible.md CSSWG issue: https://github.com/w3c/csswg-drafts/issues/6850 Element.isVisible() returns true if the element is visible, and false if it is not. It checks a variety of factors that would make an element invisible, including display:none, visibility, content-visibility, and opacity.

1 0

accounts.google.com is blocking WebKitGTK
by Michael Catanzaro 04 May '22

04 May '22

Hi, see: https://bugs.webkit.org/show_bug.cgi?id=240041 It is a little finicky, in that it *sometimes* works, and I don't know why. But usually Google blocks us. See screenshot: https://bugs.webkit.org/attachment.cgi?id=458768 I was hoping that it could be avoided by a user agent quirk, but sadly they are doing some deeper level of fingerprinting. Can anybody who is able to get attention from Google help get this reverted *urgently*? This is beyond unacceptable. I doubt we'll have any luck via the ask nicely approach, but it's worth a try. Michael

2 2

Request for position: visual-box on overflow-clip-margin
by Khushal Sagar 04 May '22

04 May '22

Hello webkit-dev, I'm seeking Webkit's position on addition of visual-box to overflow-clip-margin <https://drafts.csswg.org/css-overflow-3/#propdef-overflow-clip-margin>, discussed in this issue <https://github.com/w3c/csswg-drafts/issues/5801>. A previous RFP for this property is here <https://lists.webkit.org/pipermail/webkit-dev/2020-December/031636.html> but the syntax was extended to allow changing the box which defines the overflow clip edge. Thanks. Khushal

1 0

Request for feedback on CompressionStream and DecompressionStream
by Adam Rice 02 May '22

02 May '22

I am trying to gauge feedback on compression streams with a view to shipping them in Chromium. Very briefly, they are a way to do gzip and gunzip in the browser. Less briefly, the explainer https://github.com/WICG/compression/blob/master/explainer.md goes into some detail of the how and why. The specification https://wicg.github.io/compression/ gives verbose detail of how. You may also find the W3C TAG review https://github.com/w3ctag/design-reviews/issues/410 interesting. Any and all feedback is welcome! FAQ: Q. Will this support brotli, zstd, etc.? A. Not yet. It's on the radar. Thanks, Adam Rice, Chromium

3 3