@remote-ui/[email protected]

Patch Changes

• #522 0ade5f7 Thanks @thomas-marcucci! - Fixes an issue when removeChild does not find a child node

@remote-dom/[email protected]

Patch Changes

• #517 99a8e1a Thanks @lemonmade! - Fix missing attributes and event listeners on root receiver elements

• Updated dependencies [99a8e1a]:

  • @remote-dom/[email protected]

@remote-dom/[email protected]

Patch Changes

• #517 99a8e1a Thanks @lemonmade! - Fix missing attributes and event listeners on root receiver elements

@remote-dom/[email protected]

Patch Changes

• #492 59f417b Thanks @lemonmade! - Apply React polyfill directly to globalThis

@remote-dom/[email protected]

Patch Changes

• #465 017ca02 Thanks @lemonmade! - Fix slot to be transmitted as an attribute, not a property

• Updated dependencies [994e2ea, 017ca02]:

  • @remote-dom/[email protected]
  • @remote-dom/[email protected]

@remote-dom/[email protected]

Patch Changes

• #499 994e2ea Thanks @lemonmade! - Roll back mutation of globalThis and globalThis.self in Window.setGlobal()

  This prevents the polyfill from interfering with globals like globalThis.addEventListener, which you may need to manage the communication between a sandboxed environment and the main thread.

  In the future, we will likely change the polyfill to require you to explicitly install the polyfill, instead of it being done automatically when you @remote-dom/core/polyfill. At that point, we will reintroduce the ability to more faithfully replicate more DOM globals, like having globalThis, globalThis.self, and globalThis.window all refer to the same polyfilled Window object. To install this polyfill today and get back to the behavior introduced by this PR, you can call the new Window.setGlobalThis() method:

  import {window, Window} from '@remote-dom/core/polyfill';
  
  Window.setGlobalThis(window);

@remote-dom/[email protected]

Patch Changes

• #499 994e2ea Thanks @lemonmade! - Roll back mutation of globalThis and globalThis.self in Window.setGlobal()

  This prevents the polyfill from interfering with globals like globalThis.addEventListener, which you may need to manage the communication between a sandboxed environment and the main thread.

  In the future, we will likely change the polyfill to require you to explicitly install the polyfill, instead of it being done automatically when you @remote-dom/core/polyfill. At that point, we will reintroduce the ability to more faithfully replicate more DOM globals, like having globalThis, globalThis.self, and globalThis.window all refer to the same polyfilled Window object. To install this polyfill today and get back to the behavior introduced by this PR, you can call the new Window.setGlobalThis() method:

  import {window, Window} from '@remote-dom/core/polyfill';
  
  Window.setGlobalThis(window);

• #465 017ca02 Thanks @lemonmade! - Fix slot to be transmitted as an attribute, not a property

• Updated dependencies [994e2ea]:

  • @remote-dom/[email protected]

@remote-dom/[email protected]

Patch Changes

• #472 1473a3c Thanks @jakearchibald! - Fix removeChild so it clears parent/sibling references

• #472 1473a3c Thanks @jakearchibald! - Add node.parentElement

• #470 08839d3 Thanks @developit! - window aliases should refer to globalThis

@remote-dom/[email protected]

Minor Changes

• #446 b297fc5 Thanks @jakearchibald! - Implement node.isConnected

Patch Changes

• #446 b297fc5 Thanks @jakearchibald! - Ensure that the insert and remove hooks are only called for element parents.

• #446 b297fc5 Thanks @jakearchibald! - Make connectedCallback and disconnectedCallback call on connect/disconnect recursively

@remote-dom/[email protected]

Patch Changes

• #436 5979797 Thanks @jakearchibald! - Ensure the createText hook is called when creating a new text node