polyfills

polyfills copied to clipboard

[scoped-custom-element-registry] `importNode is not a function` on latest Chromium

2

### Description The latest version of Chromium (120) supports `ShadowRoot.prototype.createElement`. However, it does not support `ShadowRoot.prototype.importNode`. Since the polyfill uses the existence of `ShadowRoot.prototype.createElement` as a check for polyfill application,...

tlouisse

[scoped-custom-element-registry] Unconditionally install the polyfill

5

Fixes https://github.com/webcomponents/polyfills/issues/549 This is the simplest way to do it - just remove the dangerous feature check. I would maybe want to export a function to install the polyfill, but...

justinfagnani

[scoped-custom-element-registry] The polyfill should not conditionally install itself

1

The Scoped Custom Element Registry proposal is not finalized, and does not have a spec, or any native implementations. The current conditional install based on a [shallow feature detection](https://github.com/webcomponents/polyfills/blob/master/packages/scoped-custom-element-registry/src/scoped-custom-element-registry.js#L14) causes...

justinfagnani

[scoped-custom-element-registry] proof of concept to fix stand-in element issues

6

## Description [prototype new polyfill](https://lit.dev/playground/#gist=28132258a03344a3ecdf02f72ee39109) This is an alternate way to implement the custom elements registry polyfill. Instead of polyfilling `CustomElementsRegistry` completely and using a stand-in proxy element that delegates...

sorvell

[scoped-custom-element-registry] Elements can lose registry when removed from DOM

1

### Description If a nested element is removed from a shadowRoot using a registry and then `innerHTML` is called on it with html containing a scoped element, the element will...

sorvell

[scoped-custom-element-registry]: Safari v16.4 focuses all custom elements

4

### Description Safari v16.4 supports `attachInternals` and `formAssociated` features natively, and with the subject polyfill enabled _all_ custom elements on the page are keyboard-focusable using Tab key, regardless of the...

deepsweet

Install polyfill when upgrade is not a function

1

Fixes #565 Also check if `upgrade` is a function in case it is only supported on later browsers than `define` and `get`.

Jeroen-Veltmans

### Description The polyfill is not loaded when the browser version has `CustomElementRegistry.define` but doesn't have `CustomElementRegistry.upgrade`. ### Example // Uncomment below to make it work regardless // window.customElements =...

Jeroen-Veltmans

fix(scoped-custom-element-registry): resolve formAssociated getter fr…

1

This PR solves the issues https://github.com/webcomponents/polyfills/issues/547 and https://github.com/webcomponents/polyfills/issues/546 using the original definition of the formAssociated property set by the webcomponent original class.

igomezal

Bumps [parse-url](https://github.com/IonicaBizau/parse-url) to 8.1.0 and updates ancestor dependency [lerna](https://github.com/lerna/lerna/tree/HEAD/packages/lerna). These dependencies need to be updated together. Updates `parse-url` from 6.0.5 to 8.1.0 Release notes Sourced from parse-url's releases. 8.1.0 [email protected]...

dependabot[bot]