Re: [WICG/webcomponents] SVG use element can't reference an element within the same shadow tree (#772)

I can see that this question is not resolved for years...

To me, this whole decision to make shadow DOM too much cutted from outside world leads to more problems than solutions...

Why not just let it go? And make the shadow DOM features opt-in/out able ?

```javascript
elem.attachShadow({
    events: 'traverse' | 'hybrid' | 'boundary'',
    baseURI: 'parent' | 'none' | 'https://...',
    css: 'traverse' | 'confine' | 'only shared' | 'only --var',
    shadow: 'private' | 'public',
})
// actual elem.attachShadow would be something like 
elem.attachShadow({
    events: 'boundary'',
    baseURI: 'none',
    css: 'only --var',
    shadow: 'public',
})
// and complete open DOM like if .append() would add clear DOM
const shadow = elem.attachShadow({
    events: 'traverse',
    baseURI: 'parent',
    css: 'traverse',
    shadow: 'private',
})
// Note on shadow: private, it would make Element.shadowRoot undefined, 
// and the only way to access it is to keep a reference from the method call...
```

Note the vocabulary here is not a spec ^^

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

Message ID: <WICG/webcomponents/issues/772/1517991528@github.com>