Re: [WICG/webcomponents] Idea: Alternative Ways to Control Registry Scoping (Issue #1058)

For the 3rd party framework case, this seems possibly more powerful than would would strictly be needed since: (1) the main issue is interaction with the global registry not arbitrary ones, and (2) it might be feasible to limit special behavior to disconnected elements.

Here's a strawperson of what conceptually might mostly work:
```js
runWithScope = (registry, callback) => {
  const {document} = wndow;
  const {content} = document.createElement('template');
  window.document = content.ownerDocument;
  callback();
  window.document = document;
  registry.upgrade(content); 
}
```

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

Message ID: <WICG/webcomponents/issues/1058/2093715805@github.com>