Re: [w3c/webcomponents] Web Components F2F topics for 2018 TPAC (#763)

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.

 - [<iframe> and the History API](https://github.com/w3c/webcomponents/issues/184)
 - [How should various document internal references work when SVG is being used in shadow DOM](https://github.com/w3c/webcomponents/issues/179)
 - [How to define APIs only for custom element authors](https://github.com/w3c/webcomponents/issues/758)
 - [Selection APIs for Shadow DOM](https://github.com/w3c/webcomponents/issues/79)
- [It is unclear how directionality should be inherited into Shadow DOM](https://github.com/whatwg/html/issues/3699)
- [It is unclear how title attribute should work in Shadow DOM](https://github.com/whatwg/html/issues/3821)
- [elementFromPoint, elementsFromPoint, and caretPositionFromPoint should not return an element inside a shadow tree](https://github.com/w3c/csswg-drafts/issues/556)
- [Provide a lightweight mechanism to add styles to a custom element](https://github.com/w3c/webcomponents/issues/468)
- [Presence of disconnectedCallback can expedite an invocation of connectedCallback](https://github.com/w3c/webcomponents/issues/760)
- [Mechanism for setting the tabindex focus flag without sprouting tabindex attribute?](https://github.com/w3c/webcomponents/issues/762)

More issues:
* https://github.com/search?q=label%3A%22topic%3A+shadow%22+is%3Aopen
* https://github.com/search?q=label%3A%22topic%3A+custom+elements%22+is%3Aopen


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/763#issuecomment-423719623