Re: [webkit-dev] Position on emerging standard: Declarative Shadow DOM

2021-02-18 Thread Ryosuke Niwa via webkit-dev 
On Thu, Feb 18, 2021 at 3:17 PM Mason Freed via webkit-dev <
webkit-dev@lists.webkit.org> wrote:

> I just wanted to send a final heads-up that Chromium is intending to ship
> the Declarative Shadow DOM feature. We haven't heard much back from WebKit
> in the last 5 months or so, but in the meantime there has been some good
> discussion with Mozilla and the broader community. Several more performance
> investigations have been performed, around the overhead of Shadow DOM
> generally, and around the potential polyfill alternatives for DSD. You can
> see a summary of these, plus all of the other changes that we've
> incorporated, in this comment on the Mozilla Standards Position thread
> .
> These changes are the result of your (and the community's) involvement and
> feedback, so thanks. At this point, we believe all of the feedback has been
> addressed.
>

The latest proposal does solve much of the problems we've identified in the
past, and it's looking to be a promising direction. Do you have any example
website or app that you can share with which resulted in the observed 15%
improvement in FCP? That would be a very intriguing observation and would
substantiate the support for this feature.

However, as I commented on https://github.com/whatwg/dom/pull/892 and have
previously stated during the last F2F and other avenues, the currently
proposed semantics of getInnerHTML is deeply problematic. We want
consistent semantics across different kinds of Web API, and what's being
proposed is very much different from what we had discussed what we would do
for selection.

Also, have people figured out how scoped custom element registries can
integrate with this feature in the future? Given that's the other most
frequently requested feature, it would be very regrettable if we later
found out some inconsistencies or awkwardness in their integrations.

- R. Niwa

On Tue, Aug 11, 2020 at 10:27 AM Mason Freed 
> wrote:
>
>> Yes, thanks! Welcome back!
>>
>> On Mon, Aug 10, 2020 at 3:24 PM
>> - R. Niwa
>>  wrote:
>>
>>> Hi,
>>>
>>> Sorry for the late reply. I've been on a medical leave. I just
>>> commented on https://github.com/whatwg/dom/issues/831
>>>
>>> - R. Niwa
>>>
>>> On Tue, Aug 4, 2020 at 4:26 PM Mason Freed 
>>> wrote:
>>> >
>>> > Hello WebKit folks,
>>> >
>>> > I just wanted to quickly ping this thread to see if there was any
>>> interest in posting a position on declarative Shadow DOM. My original post
>>> here didn't gather much feedback. :-)
>>> >
>>> > Thanks,
>>> > Mason
>>> >
>>> >
>>> > On Tue, May 26, 2020 at 12:11 PM Mason Freed 
>>> wrote:
>>> >>
>>> >> Hello WebKit!
>>> >>
>>> >> I would like to request an official WebKit position on the
>>> Declarative Shadow DOM proposal. There have been some great comments and
>>> discussion from WebKit folks on the issue thread, but it is a bit unclear
>>> whether the overall proposal is something WebKit would support. This was
>>> brought up and discussed, e.g., on the DOM spec PR here:
>>> https://github.com/whatwg/dom/pull/858#issuecomment-623735890
>>> >>
>>> >> Please see below for all of the relevant supporting documents and
>>> discussions.
>>> >>
>>> >> Explainer:
>>> https://github.com/mfreed7/declarative-shadow-dom/blob/master/README.md
>>> >> WhatWG DOM Issue discussion: https://github.com/whatwg/dom/issues/831
>>> >> HTML Spec PR: https://github.com/whatwg/html/pull/5465
>>> >> DOM Spec PR: https://github.com/whatwg/dom/pull/858
>>> >> TAG review: https://github.com/w3ctag/design-reviews/issues/494
>>> >> Request for Mozilla Position:
>>> https://github.com/mozilla/standards-positions/issues/335
>>> >>
>>> >> Thanks,
>>> >> Mason Freed
>>> >>
>>> > ___
>>> > webkit-dev mailing list
>>> > webkit-dev@lists.webkit.org
>>> > https://lists.webkit.org/mailman/listinfo/webkit-dev
>>>
>> ___
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Position on emerging standard: Declarative Shadow DOM

2021-02-18 Thread Mason Freed via webkit-dev 
Hello WebKit,

I just wanted to send a final heads-up that Chromium is intending to ship
the Declarative Shadow DOM feature. We haven't heard much back from WebKit
in the last 5 months or so, but in the meantime there has been some good
discussion with Mozilla and the broader community. Several more performance
investigations have been performed, around the overhead of Shadow DOM
generally, and around the potential polyfill alternatives for DSD. You can
see a summary of these, plus all of the other changes that we've
incorporated, in this comment on the Mozilla Standards Position thread
.
These changes are the result of your (and the community's) involvement and
feedback, so thanks. At this point, we believe all of the feedback has been
addressed.

Thanks,
Mason


On Tue, Aug 11, 2020 at 10:27 AM Mason Freed 
wrote:

> Yes, thanks! Welcome back!
>
> On Mon, Aug 10, 2020 at 3:24 PM Ryosuke Niwa  wrote:
>
>> Hi,
>>
>> Sorry for the late reply. I've been on a medical leave. I just
>> commented on https://github.com/whatwg/dom/issues/831
>>
>> - R. Niwa
>>
>> On Tue, Aug 4, 2020 at 4:26 PM Mason Freed 
>> wrote:
>> >
>> > Hello WebKit folks,
>> >
>> > I just wanted to quickly ping this thread to see if there was any
>> interest in posting a position on declarative Shadow DOM. My original post
>> here didn't gather much feedback. :-)
>> >
>> > Thanks,
>> > Mason
>> >
>> >
>> > On Tue, May 26, 2020 at 12:11 PM Mason Freed 
>> wrote:
>> >>
>> >> Hello WebKit!
>> >>
>> >> I would like to request an official WebKit position on the Declarative
>> Shadow DOM proposal. There have been some great comments and discussion
>> from WebKit folks on the issue thread, but it is a bit unclear whether the
>> overall proposal is something WebKit would support. This was brought up and
>> discussed, e.g., on the DOM spec PR here:
>> https://github.com/whatwg/dom/pull/858#issuecomment-623735890
>> >>
>> >> Please see below for all of the relevant supporting documents and
>> discussions.
>> >>
>> >> Explainer:
>> https://github.com/mfreed7/declarative-shadow-dom/blob/master/README.md
>> >> WhatWG DOM Issue discussion: https://github.com/whatwg/dom/issues/831
>> >> HTML Spec PR: https://github.com/whatwg/html/pull/5465
>> >> DOM Spec PR: https://github.com/whatwg/dom/pull/858
>> >> TAG review: https://github.com/w3ctag/design-reviews/issues/494
>> >> Request for Mozilla Position:
>> https://github.com/mozilla/standards-positions/issues/335
>> >>
>> >> Thanks,
>> >> Mason Freed
>> >>
>> > ___
>> > webkit-dev mailing list
>> > webkit-dev@lists.webkit.org
>> > https://lists.webkit.org/mailman/listinfo/webkit-dev
>>
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Re: [webkit-dev] Request for opinion on WPT RFC 72

2021-02-18 Thread Titouan Rigoudy via webkit-dev 
Hi there,

Friendly ping. @ddragana from Mozilla has proposed a simple amendment to
the RFC: instead of overriding the address space of address ranges (e.g.
"pretend 127.1.0.1/16 is public"), they proposed translating certain IP
addresses into others for testing (e.g. "pretend 127.1.0.1 is actually
8.8.8.8"). If that seems reasonable to you, I'd like to rework the RFC and
get to work on implementing it in Chrome.

Cheers,
Titouan

On Mon, Jan 25, 2021 at 2:00 PM Titouan Rigoudy  wrote:

> Hi there,
>
> I'm seeking an opinion on Webkit's part on Web Platform Tests RFC #72
> [1], for which I filed a Webkit bug [2] some time ago. Please see the bug
> and the RFC for some more details about the proposal.
>
> Thanks,
> Titouan
>
> [1] https://github.com/web-platform-tests/rfcs/pull/72
> [2] https://bugs.webkit.org/show_bug.cgi?id=219642
>
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev