[Communication] 0.23.1 release notes

[caridy]

NOTE: This issue is supposed to provide a glance of the upcoming changes in the next release. Please, comment in this issue if you have any question, or concern, or if any of the changes will have a big impact on your team.

Breaking Changes

• <slot> elements are now appearing in the DOM. This might break CSS selectors, and querySelector calls. It can also affect composition like <ul><slot>...<li>, and for that reason, those elements should not be used in composition, only use them if you fully control them in your own template. (feat(compiler): removed compiler slotset #348)
• event.target on async events will now resolve to the highest level element in the LWC component tree. (fix(engine): allowing global listeners #404)
• We are moving back to wrapping DOM nodes in proxies, which means that in some cases unwrap may be necessary again.

New Capabilities

• assignedSlot property for any element now works as expected. It points to the <slot> element that is slotting the element or null. Keep in mind that for shadows in closed mode, this property will always be null. As the moment, the mode defaults to open. (feat(engine): slot assignedSlot property #381)

Bug Fixes

• childNodes property is now reporting the right value on elements from the template. (fix(engine): including text nodes to childNodes #389)
• eventTarget pointing to slotted elements is now correct. (fix(engine): fixing event target from slotted element #359)
• display CSS rule are now handled properly (fix: simplify style logic in template compiler #314)

New Restrictions

TBD

Relaxed Restrictions

• No more warnings about using a field called state without the @track decorator. By now, everyone should be using @track intentionally when needed, no more magic about state field. (fix(engine): remove non-track state warning #376)
• shadowRoot's childNodes property is now available. (fix(engine): shadow root childNodes #374)
• Manual mutations of properties in custom elements is now allowed. This means you can implement an input-like component that keeps the UI in sync with your internal state that represents the value of the input.

[apapko]

Closing as this has been published with 23.2 notes