lwc

lwc copied to clipboard

[synthetic shadow] [lwc:if] [slots] Error: `Failed to execute 'removeChild' on 'Node'`

1

The error `Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.` pops up in an odd edge case involving synthetic shadow,...

nolanlawson

**Is your feature request related to a problem? Please describe.** When developing code and LWR in `lwr dev` mode to test it, if you temporarily cause a syntax error in...

27pchrisl

This is a follow-up to #3693. Currently, if you do `this.ariaLabelledByElements` inside a `LightningElement`, you get null ([demo](https://stackblitz.com/edit/salesforce-lwc-ozokzs?file=src%2Fmain.js)). ```js renderedCallback() { console.log(this.ariaLabelledByElements) // always null } ``` (Note this demo...

nolanlawson

Components that do not extend LightningElement should get dev warnings for missing `@api`

3

Follow-up to https://github.com/salesforce/lwc/pull/3713 and #3758 Components that extend a non-LightningElement superclass: ```js export default class extends CustomSuperclass {} ``` ... should still get dev warnings when they declare a method...

nolanlawson

OpenTelemetry sdk for lwc

5

I could not find any project to enable opentelemetry support for lwc. It would be nice to be able to observe e2e how external systems integrate with salesforce. At the...

AllanOricil

Follow-up to #3015 Hydrated components (using `hydrateComponent`) do not support native lifecycle callbacks (even with `lwcRuntimeFlags.ENABLE_NATIVE_CUSTOM_ELEMENT_LIFECYCLE` set to true) and do not support Form Associated Custom Elements (FACE) callbacks. Hydrated...

nolanlawson

### Description When we use the if-elseif-else directives as a direct child of an iteration, we're unable to benefit from any optimization using the keys due to how the nodes...

jye-sf

What happens if the `errorCallback` throws an error? It depends on a few different factors: 1. Whether it's triggered by a mutation (e.g. `element.show = true`) or not 2. Whether...

nolanlawson

Warn on usage of `if:true` and `if:false` syntax

1

As per https://developer.salesforce.com/docs/component-library/documentation/en/lwc/create_conditional, it would be good to disallow the old syntax in the deprecated rules set.

DougMidgley

Remove usage of `lwc:dynamic`

2

Deprecate usage of `lwc:dynamic` directive in `Winter24` as it will be replaced with the new `` syntax.

jmsjtu