August 2020 - webkit-dev - lists.webkit.org

Suggesting to enable paint timing by default
by Noam Rosenthal 20 Aug '20

20 Aug '20

Following the discussion with Simon in https://bugs.webkit.org/show_bug.cgi?id=78011 Since we have a pretty stable spec (https://w3c.github.io/paint-timing/) lots of passing web platform tests, other browser vendor support and a working implementation of first contentful paint, I am planning to submit a patch to enable paint timing by default. https://bugs.webkit.org/show_bug.cgi?id=211736 Any objections? Other thoughts?

4 13

Plugin process
by Michael Catanzaro 20 Aug '20

20 Aug '20

Hi, Is anybody still using the plugin process? I understand that Safari does not allow plugins anymore. Epiphany doesn't either, nor does anything packaged in Linux distros (afaik). If nothing is using it, maybe we can delete a lot of code? Is it exposed in Apple system APIs? WebKitGTK still has an enable-plugins setting that is not yet deprecated. Probably long past time to at least deprecate it. There's also, incredibly, an enable-java setting, which I presume toggles the old Java browser plugin. I sense there must be some history behind that setting. :)

5 7

Request for position on transferable streams
by Adam Rice 18 Aug '20

18 Aug '20

Transferable streams permit you to run code like worker.postMessage(stream, [stream]) where stream is a ReadableStream, WritableStream or TransformStream and have it do what you'd expect. The explainer <https://github.com/whatwg/streams/blob/master/transferable-streams-explaine…> goes into more detail of why you'd want to do this, but briefly it provides a convenient way to do thread-offloading for streams-using code. The pull-request for the standard is at https://github.com/whatwg/streams/issues/276 and the web platform tests are at https://github.com/web-platform-tests/wpt/pull/24546. Any and all feedback is welcome! Thanks, Adam Rice, Chromium

2 2

Request for position on WebRTC Insertable Streams
by Guido Urdaneta 18 Aug '20

18 Aug '20

Hello WebKit-dev, I'd like to ask for an official position on WebRTC Insertable Streams. Specification: https://w3c.github.io/webrtc-insertable-streams/ Explainer: https://github.com/w3c/webrtc-insertable-streams/blob/master/explainer.md Chromestatus entry: https://www.chromestatus.com/feature/6321945865879552 Github repo: https://github.com/w3c/webrtc-insertable-streams WG presentation: https://youtu.be/YGYlzlKFpXA?t=1047 Thanks, Guido Urdaneta

2 1

回复：Re: Request for position on content-visibility
by huangjl_yc＠sina.com 15 Aug '20

15 Aug '20

hello webkit-devI am a newcomer to webkit。 And I had followed to download a copy of source code as https://webkit.org/webkit-on-windows/ and made a build of vs 2019、and then compiled the source code and got a executable file(minibrowser.exe)、but got a error (minibrowserlib.dll is not a valid win32 application) while running minibrowser.exe.With Tool depends I found that minibrowserlib.dll lacked more than 100 dll files whose name beginning with api-ms-win-core or API-MS-WIN-SHCORE or EXT-MS-WIN。 The things I had done are as the follow:1、install vs 2019 community edition2、install ActiveState Perl3、install ActiveState Python4、install Ruby5、install Bison6、install Gperf7、install Flex8、install CMake9、install Git10、install safari11、git clone git://git.webkit.org/WebKit.git12、perl update-webkit13、perl build-webkit --debug --no-ninja //I had comment the code related to check whether local code is the latest 14、compile the source with vs 2019 My computer enviroments is as follow:1、win102、windows sdk 10.0.19041.13、visual studio 2019 component related C++ Can anyone give me some advice ? Thanks a lot。

1 0

Request for position on content-visibility
by Vladimir Levin 15 Aug '20

15 Aug '20

Hi, I'm asking for WebKit's position on CSS property content-visibility (spec draft: https://drafts.csswg.org/css-contain-2/#content-visibility) We're currently implementing this in Chromium and intend to ship it in the near future. Please let me know your thoughts, Vladimir Levin

2 1

Considering to remove ENABLE_METER_ELEMENT flag
by Takeshi Kurosawa 14 Aug '20

14 Aug '20

Hi all, Note: I'm not affiliated with either Apple, Igalia, or Sony. It seems that the specification of <meter> element is mature and the current WebKit codebase doesn't require platform specific code to render <meter> element. I see no strong reason to have the METER_ELEMENT flag today and I think we could remove it. https://webkit-search.igalia.com/webkit/search?q=METER_ELEMENT At the time of this writing, the only port disables METER_ELEMENT flag is PlayStation. https://webkit-search.igalia.com/webkit/rev/a05c8cea48e9b0853834e0278f1926c… It would be helpful if PlayStation port could consider enabling METER_ELEMENT flag. I think PlayStation port could enable the flag as is: 1. Rendering of <meter> element falls back to platform independent user agent style sheets so no platform specific code is required. 2. There is some code in WebCore/accessibility/ that is related to <meter> element, PlayStation port disables accessibility completely so that it won't affect. If I missed something, please let me know. Best wishes, Takeshi -- Takeshi Kurosawa <taken.spc(a)gmail.com>

2 1

Request for Position on document-access proposal
by Dave Tapuska 13 Aug '20

13 Aug '20

Hi Webkit-Dev, I'd like to request an official position from webkit on the document-access <https://github.com/dtapuska/documentaccess> proposal. This proposal allows a frame tree to give up the requirement that same-origin frames might be in the same event loop via an attribute. TAG discussion was here: https://github.com/w3ctag/design-reviews/issues/397 Chromium Intent to Ship: https://groups.google.com/a/chromium.org/d/msg/blink-dev/TzuPAx9ZOk0/HYOf3F… dave.

1 0

debug-test-runner: Timed out waiting for notifyDone to be called
by Benjamin King 13 Aug '20

13 Aug '20

Hi, I’m trying to run a LayoutTest case in the debugger using `debug-test-runner` and it fails by timing out, see below. However, if I run `run-webkit-test` it works. I read the WebKit wiki on debugging and searched google to no avail. Any advice? ``` % ./Tools/Scripts/debug-test-runner LayoutTests/webaudio/biquad-lowpass.html … (lldb) run … 2020-08-13 12:30:12.960868-0400 WebKitTestRunner[73700:1010133] [Loading] 0x10a026020 - [pageProxyID=7, webPageID=8, PID=73704] WebPageProxy::didCommitLoadForFrame: frameID = 3 Content-Type: text/plain #PID UNRESPONSIVE - WebKitTestRunner (pid 73700) FAIL: Timed out waiting for notifyDone to be called #EOF #EOF #EOF … Process 73700 exited with status = 0 (0x00000000) ``` ``` % ./Tools/Scripts/run-webkit-tests LayoutTests/webaudio/biquad-lowpass.html … Running 1 test Starting helper ...2020-08-13 12:27:48.457 LayoutTestHelper[73637:1007760] Could not determine current color profile, so it will not be reset after running the tests. Running 1 WebKitTestRunner. The test ran as expected. ```

2 1

Request for position on a Link header to use Signed HTTP Exchanges to load subresources
by Tsuyoshi Horo 13 Aug '20

13 Aug '20

Hi Webkit-Dev, We're preparing to ship an extension to the HTTP Link header to allow a source site to tell the browser that subresources of a page it's prenavigating to, may be retrieved as signed exchanges from the source site. We're aware that you currently oppose the existence of signed exchanges, but we'd still appreciate your thoughts on the new use of `Link: …; rel=alternate; anchor=...`. - Explainer: https://github.com/WICG/webpackage/blob/master/explainers/signed-exchange-s… And also we'd welcome any updates on WebKit’s position about Signed HTTP Exchanges. Signed HTTP Exchanges - Explainer: https://developers.google.com/web/updates/2018/11/signed-exchanges - Specification: Signed Exchanges format: https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-response… Loading signed exchanges: https://wicg.github.io/webpackage/loading.html - ChromeStatus: https://chromestatus.com/feature/5745285984681984 Signed HTTP Exchange was launched in Chrome 73 (released in March 2019). We are planning on shipping this extension to the HTTP link header. We believe that this extension makes Signed HTTP Exchanges more useful, i.e. applicable beyond the AMP specific use-case we’ve had so far. https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/tybtqf-tdB4/… Thank you.

1 0