script: React correctly to selected attributes changes in for <option>#43582
Conversation
|
🤖 Opened new upstream WPT pull request (web-platform-tests/wpt#58694) with upstreamable changes. |
|
📝 Transplanted new upstreamable changes to existing upstream WPT pull request (web-platform-tests/wpt#58694). |
|
🔨 Triggering try run (#23460377363) for Linux (WPT) |
|
Test results for linux-wpt from try job (#23460377363): Flaky unexpected result (40)
Stable unexpected results that are known to be intermittent (15)
|
|
✨ Try run (#23460377363) succeeded. |
|
I would be curious to see if the same bug occurs when using the .selected IDL property (which doesn't reflect to the selected attribute). Might be that this needs handling inside of selectedness changing rather than just the attribute. |
|
📝 Transplanted new upstreamable changes to existing upstream WPT pull request (web-platform-tests/wpt#58694). |
|
I also checked the .selected path ,the sync logic is already working there. I added a few simple tests for both single and multiple select using .selected, plus one to confirm it doesn’t reflect :) |
|
I've just tested this with my select multiple PR and it fixes the two error cases I came across. |
selected attributes changes in for <option>
|
✍ Updated existing upstream WPT pull request (web-platform-tests/wpt#58694) title and body. |
1 similar comment
|
✍ Updated existing upstream WPT pull request (web-platform-tests/wpt#58694) title and body. |
|
📝 Transplanted new upstreamable changes to existing upstream WPT pull request (web-platform-tests/wpt#58694). |
Fixes: #43522