script: Improvements to command button implementation#42883
Conversation
|
Some small changes that should get the implementation good enough to then remove the feature flag. |
|
🔨 Triggering try run (#22453353601) for Linux (WPT) |
|
Test results for linux-wpt from try job (#22453353601): Flaky unexpected result (28)
Stable unexpected results that are known to be intermittent (18)
|
|
✨ Try run (#22453353601) succeeded. |
command button implementation
5c18193 to
a28ae62
Compare
|
Not sure why the try didn't catch it, but it seems there are new passes in |
a28ae62 to
07c0ba7
Compare
|
it got renamed upstream and seems it synced into main but was deleted here, something weird with a conflict. |
|
🔨 Triggering try run (#22638748659) for Linux (WPT) |
|
Test results for linux-wpt from try job (#22638748659): Flaky unexpected result (24)
Stable unexpected results that are known to be intermittent (16)
|
|
|
|
Test results for linux-wpt from try job (#22638748659): Flaky unexpected result (2)Stable unexpected results that are known to be intermittent (1)
|
|
|
|
🔨 Triggering try run (#22676300990) for Linux (WPT) |
- Correctly handle the button's optional value concept - Add the button as the source value for the CommandEvent - Fix handling of buttons in auto state Signed-off-by: Luke Warlow <[email protected]>
|
Test results for linux-wpt from try job (#22676300990): Flaky unexpected result (44)
Stable unexpected results that are known to be intermittent (12)
Stable unexpected results (22)
|
|
|
Improvements to command button implementation - Correctly handle the button's optional value concept - Add the button as the source value for the CommandEvent - Fix handling of buttons in auto state Testing: Existing tests Signed-off-by: Luke Warlow <[email protected]>
Improvements to command button implementation
Testing: Existing tests