It occurs to me that the best way to solve this may be to just not render value or checked at all in SSR'd HTML or static-optimized HTML. This would align with the historical behavior as well as the non-static-
Assignees No one assigned Labels BUG P2 enhancement perf Projects None yet Milestone No milestone Development Successfully merging a pull request may close this issue. perf(template-compiler): support key in static content salesforce/lwc 1 participant ...
Offers aserverlesshosting model where AWS manages resource scaling automatically. Staging Virtual Servers (AWS EC2) Used for launchingvirtual serversand manually configuring necessary software. Best suited for organizations withcomplex infrastructure and high traffic. Requires expertise in AWS services likeEC2...
Due to the static content optimization, the ordering of attributes in the DOM may be inconsistent. This is only an issue if you are relying on the iteration order ofelm.attributes, or the exact string output ofelm.outerHTML, or something like that. Our Jest serializer alsopretty-prints HTML,...
Description The onload event does not fire for an without a src because the event listener is added after the has already been inserted into the DOM. This only occurs when the is optimized by the static content...