polyfills

polyfills copied to clipboard

window.__shady_native_addEventListener is not a function in versions of Chrome and Firefox

8

### Description Simply trying to load the webcomponents polyfills in Firefox 30 throws this error: TypeError: window.__shady_native_addEventListener is not a function Since windows.EventTarget exists in FF30, this [if-check](https://github.com/webcomponents/polyfills/blob/fd0ebcdbb6ea330b754f04c2c9cf91aba15b2d17/packages/shadydom/src/patch-native.js#L109) results in...

rattai

[scoped-custom-element-registry] Add module flag to scoped-custom-element-registry

2

When trying to use `@webcomponents/scoped-custom-element-registry` [through unpkg using the `?module` flag](https://unpkg.com/@webcomponents/[email protected]?module), unpkg throws an error since the package doesn't include a module entry point While [removing the `?module` flag in...

alangdm

[scoped-custom-element-registry] Move tests to packages/tests/

3

The tests for this package should be moved to `packages/tests/` and added to `wct.conf.json`.

bicknellr

[scoped-custom-element-registry] Integrate and test with custom-elements polyfill

1

Task: The [scoped-custom-element-registry](https://github.com/webcomponents/polyfills/tree/master/packages/scoped-custom-element-registry) polyfill is currently only tested to work on browsers implementing the native web components specs (Custom Elements & Shadow DOM). This task is to investigate and make...

kevinpschaaf

[scoped-custom-element-registry] Add benchmarks

1

Task: The [scoped-custom-element-registry](https://github.com/webcomponents/polyfills/tree/master/packages/scoped-custom-element-registry), while building upon native Custom Elements where possible, adds some indirection, which is expected to add some measurable cost to element upgrade. It would be good to...

kevinpschaaf

[scoped-custom-element-registry] Integrate and test with shady-dom/shady-css polyfill

1

Task: The [scoped-custom-element-registry](https://github.com/webcomponents/polyfills/tree/master/packages/scoped-custom-element-registry) polyfill is currently only tested to work on browsers implementing the native web components specs (Custom Elements & Shadow DOM). This task is to investigate and make...

kevinpschaaf

[scoped-custom-element-registry] Convert to TypeScript

1

Task: The [scoped-custom-element-registry](https://github.com/webcomponents/polyfills/tree/master/packages/scoped-custom-element-registry) polyfill was prototyped in JavaScript, but should be upgraded to TypeScript to match the conventions of the monorepo.

kevinpschaaf

How to make custom web components work in ie11 using Parcel v2 and Babel?

1

I have a simple app using parcel v2 along with Babel and i want to make it compatible with ie11. The problem i am currently facing is a JS error...

VelynnXV

[Custom Elements] Incorrect `observedAttributes` behavior when using mixed-case attributes

6

### Description Another issue that is somewhat related, and may be relevant to also see for context: https://github.com/webcomponents/polyfills/issues/111 With native Custom Elements, the attributes declared in the static `observedAttributes` getter...

wessberg

es5 browsers not supported?

3

### Description `custom-elements-es5-adapter.js` contains ES2015 syntax (e.g. `const e=HTMLElement`) and thus cannot be used as a shim for es5 code without compiling, but it specifically says not to compile it...

kevinbeal