lwc icon indicating copy to clipboard operation
lwc copied to clipboard

⚡️ LWC - A Blazing Fast, Enterprise-Grade Web Components Foundation

Results 279 lwc issues
Sort by recently updated
recently updated
newest added

### Description Because of the [global monkey-patching](https://github.com/salesforce/lwc/blob/7b0418c79e4159c5a8d0f8bda5ded0f1cf312ce7/packages/%40lwc/engine-dom/src/apis/create-element.ts#L63-L82) for synthetic custom element lifecycle, we actually swallow some errors that the browser would normally throw for improper usages of the `insertBefore` API....

bug

We use non-standard mechanisms to trigger `connectedCallback`/`disconnectedCallback`. We should just use the native mechanism instead. https://github.com/salesforce/lwc/blob/551f6349421f3cfaf4e8c4a8d3d393b7549bb0ab/packages/@lwc/engine-dom/src/apis/create-element.ts#L50-L72 This has implications for backwards compat, because the timing and other subtleties will be...

BUG P3

### Description The element returned by `createElement` is an HTML element with all of the `@api`-decorated properties from the provided component class. And we see, from usage, that it is...

bug
typescript

### Description When using a template list (`for:each` or `iterator:*`), if that list contains other LWC components, then after a reordering of the list, it is possible for a component...

bug
BUG P3

### Description I wanted to bring some subtle SSR hydration mismatch issue to your attention. This gist: If you happen to have a construct like `class={classGetter}` in a template, and...

bug
SSR

**Is your feature request related to a problem? Please describe.** More and more libraries are leveraging the `.mjs` file extension for their ES Modules. The LWC transformer code only looks...

enhancement

### Description The current design of shadow DOM mixed mode is that `shadowSupportMode` only applies transitively to _children_, not to slot contents. However, similar to recent issues with native custom...

bug

_**Edit**: there is now an [RFC](https://github.com/salesforce/lwc-rfcs/pull/89)._ #4249 indicates that it may not be safe to compose native and synthetic lifecycle components together. For that reason, we should perhaps treat it...

enhancement

_**TL;DR**: No matter what, there will be some observable difference if a synthetic-lifecycle component is slotted into a native-lifecycle component._ As demonstrated by #4248, we have some issues where we...

bug