Native support for Shadow DOM v1 is hitting browsers, and Polymer v2 was just released. I am requesting support for Shadow DOM as a feature because there are just too many bugs to try to describe. When Trix is placed inside a ShadowRoot, it is broken in many ways.

• It is not binding to the hidden input field. This may be due to needing to perform query selectors using the Shadow Root instead of document?

• It is not binding to a custom toolbar (probably same issue as above) but with the added fun that now inputing text is displayed right to left (fun).

• The native toolbar is not applying selection formatting for bold/italic/subscript correctly. This is probably due to needing to use ShadowRoot.getSelection() rather than document or window getSelection().

Rather than try to have the community try to document and submit what may be a lot of seperate behavior bugs, I suggest that the project team needs to take on the specific task of making all the existing demos/samples and tests work in Shadow DOM and issue a future release with support for Shadow DOM a specific feature.