[webkit-dev] What do we do with various Web component features?

[Antti Koivisto]

I agree that we should remove most of the Shadow DOM related code (the
portions supporting distribution especially). It is invasive, has
significant architectural issues (including use of a confusing mutating
iterator) and forces generic code many places where it would not be needed
otherwise. It is essentially blocking us from improving DOM data
structures. The code has been developed organically in parallel with the
spec and I feel that a future new implementation could be cleaner.


   antti



On Sat, Apr 27, 2013 at 2:38 PM, Benjamin Poulain <benjamin at webkit.org>wrote:

> On Fri, Apr 26, 2013 at 9:46 PM, Ryosuke Niwa <rniwa at webkit.org> wrote:
>
>> There appears to be a lot of Web component related features in
>> WebKit that used to be maintained by Chromium contributors;
>> specifically those related to Shadow DOM and node distributions.
>>
>> What do we do with them? The specification is still under the
>> construction and our implementation is getting outdated day by day.
>>
>> I certainly see the value of the proposed specification, and I would like
>> it to be shipped by WebKit browsers. However, having unmaintained code that
>> is this invasive in WebCore is very harmful in short term.
>>
>> Is anyone stepping up to maintain the code, or should we consider
>> removing them for the time being?
>>
>
> All that unmaintained code has a cost we should not have to pay.
>
> I am in favor of removing it and bring the code back later when someone
> decide to support that spec.
>
> Benjamin
>
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20130429/e88d66d7/attachment.html>