Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile
Hayato (Shadow DOM)

@shadow_hayato

Google, Software Engineer. Tech Lead of DOM and Web Components in Google Chrome. Ping @hayatoito at GitHub.

ID: 2179824044

linkhttp://hayato.io/ calendar_today07-11-2013 10:33:59

212 Tweet

895 Takipçi

18 Takip Edilen

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

I've been asked, "You are a tech lead of DOM team? So, what is DOM team working on?". Let me use this twitter account to report that briefly. See sites.google.com/a/chromium.org… to know dom-team in chromium.

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

Regarding Web Components, we are still working hard. We will ship Incremental Shadow DOM at Chrome M69, which is purely the performance improvement of rendering pipeline from web developer's perspective.

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

We are working on CSS Shadow Parts (::part) to make Web Components easily stylable. See this nice explainer, meowni.ca/posts/part-the….

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

We are working on "Custom Elements Default Style" so that custom elements themselves are stylable cheaply and easily. See this loooong discussion, if you are interested in, github.com/w3c/webcompone…

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

We are working on constructable CSS Stylesheets so that stylesheets can be shared and re-used by Web Components cheaply. We don't want to load nor parse the same stylesheet again and again. See tabatkins.github.io/specs/construc….

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

We are planning on deprecate and remove Shadow DOM v0 and Custom Elements v0 from Blink. Shadow DOM v0 and Custom Element v0 are NOT *Web*. They are only available on Google Chrome. If you are still using v0 APIs, please consider to migrate to v1 seriously.

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

We are working on Form participation APIs so that elements other than built-in elements can participate in Form submission. See this explainer docs.google.com/document/d/1JO…

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

To make DOM and HTML more pleasant to use, we are shipping element.toggleAttribute: dom.spec.whatwg.org/#dom-element-t…. I am always fan of implementing these small but nice uncontroversial APIs which would make developers happy surely.

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

The other planned projects: Scoped Custom Elements Registries to avoid name collision. See github.com/w3c/webcompone…. Find-in-Page improvements: github.com/rakina/find-in…. Template Instantiation: github.com/w3c/webcompone…. Imperative shadow DOM distribution API: github.com/whatwg/html/is…

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

These don't cover all projects we are working on. We are also working on other projects, however, I hope you can enjoy this report. I'll do the status report again at the end of Q3. See you later!

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

Intent to implement: Searchable Invisible DOM. This idea is very early-stage. We are exploring. groups.google.com/a/chromium.org…

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

I am glad to hear that React folks might simplify their event system and make it closer to the platform's DOM events. github.com/facebook/react…

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

Microsoft Edge has started to implement Shadow DOM v1 and Custom Elements v1 developer.microsoft.com/en-us/microsof… developer.microsoft.com/en-us/microsof…

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

Let me share the brief summary of “Google’s position” on each topic of Web Components at TPAC 2018. docs.google.com/document/d/1HP…

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

We are shipping CSS Shadow Parts (::part pseudo elements) in Chrome 73. Another important primitive, ::theme, will follow hopefully. chromium-review.googlesource.com/c/chromium/src…

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

We are shipping Constructable Stylesheets in Chrome 73. This would make style usages in shadow trees much faster. developers.google.com/web/updates/20… The further background why we need is here: crbug.com/712080

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

I've posted a straw-man proposal for Imperative Shadow DOM Distribution API here. Feedback is welcomed. github.com/w3c/webcompone…

Hayato (Shadow DOM) (@shadow_hayato) 's Twitter Profile Photo

Shipping "IncrementalShadowDOM" in Google Chrome M68. This is the first major re-architect of Shadow DOM implementation in Blink. Hoping to make Web Components apps much faster and responsive. groups.google.com/a/chromium.org…