Skip to content

Issue with shadow dom elements #10

@rjaponte

Description

@rjaponte

With how shadow dom elements are in a separate scope that requires knowing the parent element has a shadowRoot there is a gap in covering this use case with the prototyper. To resolve this issue there would have to be a way to detect that an element has a shadowRoot with elements that need to be converted.

The hardest part is how some elements' shadowRoot uses assigned elements to tie elements that are siblings of the shadowRoot for said element.

A view would be something like the following:

app-element
--shadowRoot
----div
------section.nav(assigned)
--section.nav
----ul
...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions