Hi all, I've successfully finished the prototype of custom elements, and attended a F2F meeting in January [1]. We had reached consensus on many pressing matters, and now we have a rewrite of the spec based on this meeting [2].
As such, now I'm going to proceed to implement custom elements API for real in trunk WebKit behind a build flag without prefix and enable it by default on Mac ports (as done for the prototype). You can follow the new implementation effort on https://webkit.org/b/154907 [1] https://github.com/w3c/WebPlatformWG/blob/gh-pages/meetings/25janWC.md [2] https://github.com/w3c/webcomponents/pull/405 - R. Niwa On Wed, Nov 18, 2015 at 6:35 PM, Ryosuke Niwa <rn...@webkit.org> wrote: > Hi all, > > I would like to start prototyping custom elements API in WebKit. > Custom elements API allows authors to define a author-defined tag name > associated with its own JS interface. There is a draft spec proposed > by Google (http://w3c.github.io/webcomponents/spec/custom/) but there > has been many open questions regarding the construction timing and > mechanism: > https://github.com/w3c/webcomponents/tree/gh-pages/proposals > > Unfortunately, many of those open questions are hard to answer without > further implementation experience and feedback as well as Web > developer feedback. As such, I've started prototyping what we've been > discussing at W3C and posted work-in-progress patches on > webkit.org/b/150225. > > Since it's troublesome for developers to build trunk WebKit with my > changes, I plan to land my experimental API on trunk WebKit behind a > build flag, enabled it by default for Mac port (as done for shadow DOM > API). > > Please let me know if you have any concerns and/or comments. > > - R. Niwa _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
