Web Components F2F topics for 2018 TPAC #763

rniwa · 2018-08-29T05:21:29Z

We should gather topics which needs F2F discussion. I propose the following topics:

<iframe> and the History API
How should various document internal references work when SVG is being used in shadow DOM
How to define APIs only for custom element authors

Please add more topics to this issue so that each browser vendor can have their internal discussion upfront (this seems to have helped a lot in the past).

@domenic @tkent-google @hayatoito @annevk @bzbarsky @smaug---- @travisleithead

smaug---- · 2018-08-29T08:45:02Z

Selection handling + shadow DOM is something to figure out, #79

hayatoito · 2018-08-29T08:55:11Z

I think we need to have a consensus on:

It is unclear how directionality should be inherited into Shadow DOM

And other attributes:

hayatoito · 2018-08-29T09:27:26Z

One more topic candidate:

elementFromPoint, elementsFromPoint, and caretPositionFromPoint should not return an element inside a shadow tree

cc: @rakina, @yosinch

hayatoito · 2018-08-29T09:31:31Z

One more: Custom Elements Default Style

cc: @emilio, @lilles

rniwa · 2018-08-30T05:10:21Z

I'd add my own: Presence of disconnectedCallback can expedite an invocation of connectedCallback

matthewp · 2018-08-30T12:53:55Z

@rniwa That link is to your own comment in this issue, I assume this was a mistake and you intended to link to something else?

abdonrd · 2018-08-30T14:49:24Z

@rniwa @matthewp probably to: #760

rniwa · 2018-08-30T23:27:03Z

Yeah, fixed.

rniwa · 2018-08-31T00:06:44Z

DOM APIs which replace all children end up firing superfluous slotchange events

annevk · 2018-09-07T14:53:33Z

https://github.com/w3c/webcomponents/labels/needs%20implementer%20interest are presumably worth discussing as well, in particular "CSS Modules".

And then there's always all of these:

rniwa · 2018-09-08T23:15:19Z

Given how many topics we have to discuss, I suggest we schedule some time on Wed breakout sessions if we don't get an extra room on Tuesday.

chaals · 2018-09-09T21:55:37Z

(Note that we have requested extra space if there is any... but there are no guarantees)

rniwa · 2018-09-22T06:04:32Z

Here's the list of explicitly requested topics. Please call out other issues as you see fit. Let's finalize the list beforehand so that each participating organizations can have their own internal discussion first.

More issues:

rniwa · 2018-10-03T00:10:32Z

Hi all, thanks to @LJWatson, we now have a room available on Tuesday in addition to Friday but the room for Tuesday doesn't have a teleconference capability.

Do people have preference over which topic to be discussed on Tuesday (in-person only) vs. Friday (allows remote participation)? Please comment here ASAP.

chaals · 2018-10-03T00:15:40Z

The space we have is for THURSDAY (9.00 - 13.30). Also note that it is a fairly small room (space for ~15, no phone bridge)... /@rniwa

rniwa · 2018-10-03T00:16:18Z

@chaals : Ah, okay. Thanks for correcting my mistake & clarification!

yoichio · 2018-10-03T05:11:39Z

I want to have a brainstorming session for "(better) Selection APIs for Shadow DOM" .

rniwa · 2018-10-03T05:17:17Z

@yoichio : Selection APIs for Shadow DOM is listed as a topic.

rniwa · 2018-10-04T21:33:19Z

Here's my proposal for Thursday / Friday breakdown. Please raise your concerns if the topic you care about is placed in a wrong day. I've tried to place all accessibility & CSS related topics on Friday since Houdini and ARIA WG are meeting on Thursday.

Thursday morning :

<iframe> and the History API
Selection APIs for Shadow DOM
Scoped Custom Element Registries
It is unclear how title attribute should work in Shadow DOM
Presence of disconnectedCallback can expedite an invocation of connectedCallback
Issue triaging as the time permits

More issues:

Friday afternoon:

rniwa · 2018-10-22T08:08:06Z

Update: How should various document internal references work when SVG is being used in shadow DOM may need to move to Monday afternoon if Tab Atkins can't attend it on Thursday. If you have any concerns about this agenda change, please comment here ASAP.

hayatoito · 2018-10-22T09:03:15Z

Let me share the brief summary of “Google’s position” on each topics of Web Components at TPAC 2018.

Please consider this one-pager as just on-going efforts. Anything is not finalized, and can be changed, given recent increased discussion on several topics.

https://bugs.webkit.org/show_bug.cgi?id=157437 <rdar://problem/26154021> Reviewed by Simon Fraser. Source/WebCore: Update the WebKit's treatment of shadow boundaries in offsetLeft, offsetTop, and offsetParent to match the latest discussion in CSS WG. See WICG/webcomponents#497 and WICG/webcomponents#763 The latest consensus is to use the retargeting algorithm (https://dom.spec.whatwg.org/#retarget). In practice, this would mean that we need to keep walking up the offset parent ancestors until we find the one which is in the same tree as a shadow-inclusive ancestor of the context object. For example, if a node (the context object of offsetTop, offsetLeft, offsetParent) was assigned to a slot inside a shadow tree and its offset parent was in the shadow tree, we need to walk up to its offset parent, then its offset parent, etc... until we find the offset parent in the same tree as the context object. Note it's possible that the context object is inside a shadow tree which does not have its own offset parent. (e.g. all elements have position: static) For this reason, we need to consider not just offset parent in the same tree as the context object but as well as any offset parent which is in its ancestor trees. Test: fast/shadow-dom/offsetParent-across-shadow-boundaries.html * dom/Element.cpp: (WebCore::adjustOffsetForZoomAndSubpixelLayout): Extracted to share code between offsetLeft and offsetTop. (WebCore::collectAncestorTreeScopeAsHashSet): Added. (WebCore::Element::offsetLeftForBindings): Added. Sums up offsetLeft's until it finds the first offset parent which is a shadow-including ancestor (https://dom.spec.whatwg.org/#concept-shadow-including-ancestor). (WebCore::Element::offsetLeft): Now uses adjustOffsetForZoomAndSubpixelLayout. (WebCore::Element::offsetTopForBindings): Added. Like offsetLeftForBindings, this function sums up offsetTop's until it finds the first offset parent which is a shadow-including ancestor. (WebCore::Element::offsetTop): Now uses adjustOffsetForZoomAndSubpixelLayout. (WebCore::Element::offsetParentForBindings): Renamed from bindingsOffsetParent to be consistent with other functions meant to be used for bindings code. * dom/Element.h: * html/HTMLElement.idl: Source/WebKit: Use *forBindings variants of offsetLeft, offsetTop, and offsetParent. * WebProcess/InjectedBundle/API/gtk/DOM/WebKitDOMElementGtk.cpp: (webkit_dom_element_get_offset_left): (webkit_dom_element_get_offset_top): (webkit_dom_element_get_offset_parent): Source/WebKitLegacy/mac: Use *forBindings variants of offsetLeft, offsetTop, and offsetParent. * DOM/DOMElement.mm: (-[DOMElement offsetLeft]): (-[DOMElement offsetTop]): (-[DOMElement offsetParent]): LayoutTests: Added a W3C style testharness.js test. * fast/shadow-dom/offsetParent-across-shadow-boundaries-expected.txt: Added. * fast/shadow-dom/offsetParent-across-shadow-boundaries.html: Added. git-svn-id: http://svn.webkit.org/repository/webkit/trunk@239313 268f45cc-cd09-0410-ab3c-d52691b4dbfc

https://bugs.webkit.org/show_bug.cgi?id=157437 <rdar://problem/26154021> Reviewed by Simon Fraser. Source/WebCore: Update the WebKit's treatment of shadow boundaries in offsetLeft, offsetTop, and offsetParent to match the latest discussion in CSS WG. See WICG/webcomponents#497 and WICG/webcomponents#763 The latest consensus is to use the retargeting algorithm (https://dom.spec.whatwg.org/#retarget). In practice, this would mean that we need to keep walking up the offset parent ancestors until we find the one which is in the same tree as a shadow-inclusive ancestor of the context object. For example, if a node (the context object of offsetTop, offsetLeft, offsetParent) was assigned to a slot inside a shadow tree and its offset parent was in the shadow tree, we need to walk up to its offset parent, then its offset parent, etc... until we find the offset parent in the same tree as the context object. Note it's possible that the context object is inside a shadow tree which does not have its own offset parent. (e.g. all elements have position: static) For this reason, we need to consider not just offset parent in the same tree as the context object but as well as any offset parent which is in its ancestor trees. Test: fast/shadow-dom/offsetParent-across-shadow-boundaries.html * dom/Element.cpp: (WebCore::adjustOffsetForZoomAndSubpixelLayout): Extracted to share code between offsetLeft and offsetTop. (WebCore::collectAncestorTreeScopeAsHashSet): Added. (WebCore::Element::offsetLeftForBindings): Added. Sums up offsetLeft's until it finds the first offset parent which is a shadow-including ancestor (https://dom.spec.whatwg.org/#concept-shadow-including-ancestor). (WebCore::Element::offsetLeft): Now uses adjustOffsetForZoomAndSubpixelLayout. (WebCore::Element::offsetTopForBindings): Added. Like offsetLeftForBindings, this function sums up offsetTop's until it finds the first offset parent which is a shadow-including ancestor. (WebCore::Element::offsetTop): Now uses adjustOffsetForZoomAndSubpixelLayout. (WebCore::Element::offsetParentForBindings): Renamed from bindingsOffsetParent to be consistent with other functions meant to be used for bindings code. * dom/Element.h: * html/HTMLElement.idl: Source/WebKit: Use *forBindings variants of offsetLeft, offsetTop, and offsetParent. * WebProcess/InjectedBundle/API/gtk/DOM/WebKitDOMElementGtk.cpp: (webkit_dom_element_get_offset_left): (webkit_dom_element_get_offset_top): (webkit_dom_element_get_offset_parent): Source/WebKitLegacy/mac: Use *forBindings variants of offsetLeft, offsetTop, and offsetParent. * DOM/DOMElement.mm: (-[DOMElement offsetLeft]): (-[DOMElement offsetTop]): (-[DOMElement offsetParent]): LayoutTests: Added a W3C style testharness.js test. * fast/shadow-dom/offsetParent-across-shadow-boundaries-expected.txt: Added. * fast/shadow-dom/offsetParent-across-shadow-boundaries.html: Added. Canonical link: https://commits.webkit.org/207360@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@239313 268f45cc-cd09-0410-ab3c-d52691b4dbfc

annevk mentioned this issue Sep 7, 2018

Agendas: TPAC 2018 w3c/WebPlatformWG#120

Closed

web-padawan mentioned this issue Oct 3, 2018

Wrap Quill and add value property vaadin/vaadin-rich-text-editor#2

Closed

snuggs mentioned this issue Dec 13, 2018

Current Status of Webcomponents devpunks/snuggsi#71

Open

rniwa closed this as completed Jan 29, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Web Components F2F topics for 2018 TPAC #763

Web Components F2F topics for 2018 TPAC #763

rniwa commented Aug 29, 2018 •

edited

Loading

smaug---- commented Aug 29, 2018

hayatoito commented Aug 29, 2018 •

edited by rniwa

Loading

hayatoito commented Aug 29, 2018 •

edited

Loading

hayatoito commented Aug 29, 2018 •

edited

Loading

rniwa commented Aug 30, 2018 •

edited

Loading

matthewp commented Aug 30, 2018

abdonrd commented Aug 30, 2018

rniwa commented Aug 30, 2018

rniwa commented Aug 31, 2018

annevk commented Sep 7, 2018

rniwa commented Sep 8, 2018

chaals commented Sep 9, 2018

rniwa commented Sep 22, 2018 •

edited

Loading

rniwa commented Oct 3, 2018

chaals commented Oct 3, 2018

rniwa commented Oct 3, 2018

yoichio commented Oct 3, 2018

rniwa commented Oct 3, 2018

rniwa commented Oct 4, 2018

rniwa commented Oct 22, 2018

hayatoito commented Oct 22, 2018

Web Components F2F topics for 2018 TPAC #763

Web Components F2F topics for 2018 TPAC #763

Comments

rniwa commented Aug 29, 2018 • edited Loading

smaug---- commented Aug 29, 2018

hayatoito commented Aug 29, 2018 • edited by rniwa Loading

hayatoito commented Aug 29, 2018 • edited Loading

hayatoito commented Aug 29, 2018 • edited Loading

rniwa commented Aug 30, 2018 • edited Loading

matthewp commented Aug 30, 2018

abdonrd commented Aug 30, 2018

rniwa commented Aug 30, 2018

rniwa commented Aug 31, 2018

annevk commented Sep 7, 2018

rniwa commented Sep 8, 2018

chaals commented Sep 9, 2018

rniwa commented Sep 22, 2018 • edited Loading

rniwa commented Oct 3, 2018

chaals commented Oct 3, 2018

rniwa commented Oct 3, 2018

yoichio commented Oct 3, 2018

rniwa commented Oct 3, 2018

rniwa commented Oct 4, 2018

rniwa commented Oct 22, 2018

hayatoito commented Oct 22, 2018

rniwa commented Aug 29, 2018 •

edited

Loading

hayatoito commented Aug 29, 2018 •

edited by rniwa

Loading

hayatoito commented Aug 29, 2018 •

edited

Loading

hayatoito commented Aug 29, 2018 •

edited

Loading

rniwa commented Aug 30, 2018 •

edited

Loading

rniwa commented Sep 22, 2018 •

edited

Loading