Context
This follow-up task was identified during the review of PR #81.
Source PR: #81
PR Title: fix(morphdom): preserve checkbox/radio checked state across updates
Suggested by: @claude[bot]
Task Description
The data-lvt-force-update attribute has a known limitation with radio buttons: sending it on only one radio in a group can silently uncheck a sibling that morphdom already processed earlier in the same pass (due to browser mutual exclusion firing synchronously mid-loop).
The workaround — send data-lvt-force-update on all radios in the group, not just the one being checked — is documented in the source code comments but not in any user-facing documentation.
A user who only sends the attribute on the radio they want checked will silently get wrong behavior. This warning should be surfaced in the public docs for the data-lvt-force-update attribute.
Priority
Low — edge case, but important for users who use force-update with radio groups.
This issue was automatically created from PR review comments.
Context
This follow-up task was identified during the review of PR #81.
Source PR: #81
PR Title: fix(morphdom): preserve checkbox/radio checked state across updates
Suggested by: @claude[bot]
Task Description
The
data-lvt-force-updateattribute has a known limitation with radio buttons: sending it on only one radio in a group can silently uncheck a sibling that morphdom already processed earlier in the same pass (due to browser mutual exclusion firing synchronously mid-loop).The workaround — send
data-lvt-force-updateon all radios in the group, not just the one being checked — is documented in the source code comments but not in any user-facing documentation.A user who only sends the attribute on the radio they want checked will silently get wrong behavior. This warning should be surfaced in the public docs for the
data-lvt-force-updateattribute.Priority
Low — edge case, but important for users who use force-update with radio groups.
This issue was automatically created from PR review comments.