@lwc/synthetic-shadow 8.11.0 → 8.12.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -6,6 +6,6 @@ This is a polyfill for ShadowRoot that was tailor-made for LWC in order to meet
6
6
 
7
7
  ## Compromises
8
8
 
9
- - Default content for `<slot>` elements is always empty.
10
- - `slotchange` is only available directly on the `<slot>` (it doesn't bubble as in the case of the native implementation). This restriction is in place because implementing `slotchange` requires using `MutationObserver` which is expensive at runtime. By only supporting `slotchange` event applied directly on the `<slot>` element, the LWC engine receives a clear signal that the component author is interested in listening to this event. This avoids spending unnecessary CPU time when the `slotchange` event is never consumed.
11
- - If you use `MutationObserver` to watch changes in a DOM tree, disconnect it or you will cause a memory leak. Note that a component can observe mutations only in its own template. It can't observe mutations within the shadow tree of other custom elements.
9
+ - Default content for `<slot>` elements is always empty.
10
+ - `slotchange` is only available directly on the `<slot>` (it doesn't bubble as in the case of the native implementation). This restriction is in place because implementing `slotchange` requires using `MutationObserver` which is expensive at runtime. By only supporting `slotchange` event applied directly on the `<slot>` element, the LWC engine receives a clear signal that the component author is interested in listening to this event. This avoids spending unnecessary CPU time when the `slotchange` event is never consumed.
11
+ - If you use `MutationObserver` to watch changes in a DOM tree, disconnect it or you will cause a memory leak. Note that a component can observe mutations only in its own template. It can't observe mutations within the shadow tree of other custom elements.
package/dist/index.cjs.js CHANGED
@@ -217,7 +217,7 @@ const KEY__LEGACY_SHADOW_TOKEN_PRIVATE = '$$LegacyShadowTokenKey$$';
217
217
  const KEY__SYNTHETIC_MODE = '$$lwc-synthetic-mode';
218
218
  const KEY__NATIVE_GET_ELEMENT_BY_ID = '$nativeGetElementById$';
219
219
  const KEY__NATIVE_QUERY_SELECTOR_ALL = '$nativeQuerySelectorAll$';
220
- /** version: 8.11.0 */
220
+ /** version: 8.12.0 */
221
221
 
222
222
  /**
223
223
  * Copyright (c) 2024 Salesforce, Inc.
@@ -225,7 +225,7 @@ const KEY__NATIVE_QUERY_SELECTOR_ALL = '$nativeQuerySelectorAll$';
225
225
  if (!globalThis.lwcRuntimeFlags) {
226
226
  Object.defineProperty(globalThis, 'lwcRuntimeFlags', { value: create(null) });
227
227
  }
228
- /** version: 8.11.0 */
228
+ /** version: 8.12.0 */
229
229
 
230
230
  /*
231
231
  * Copyright (c) 2018, salesforce.com, inc.
@@ -4383,6 +4383,6 @@ defineProperty(Element.prototype, '$domManual$', {
4383
4383
  },
4384
4384
  configurable: true,
4385
4385
  });
4386
- /** version: 8.11.0 */
4386
+ /** version: 8.12.0 */
4387
4387
  }
4388
4388
  //# sourceMappingURL=index.cjs.js.map