provide a way to un-inert it. Authors have found that accidentallyfyi, "authors" here refers to bramus, who set all:unset on a customizable select button and was confused by the form submission behavior and asked me about it.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
I have some mixed feelings about using `!important` in UA sheets, but I guess this LGTM.
provide a way to un-inert it. Authors have found that accidentallyfyi, "authors" here refers to bramus, who set all:unset on a customizable select button and was confused by the form submission behavior and asked me about it.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Commit-Queue | +2 |
I have some mixed feelings about using `!important` in UA sheets, but I guess this LGTM.
Alternatively we could go back to hard coding the intertness in c++ which I removed from HTMLButtonElement some time ago, but the functionality is the same I think. The inert attribute also sets interactivity:inert!important I think, so this is a better signal to anyone looking at styles that the button is inert.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Set interactivity:inert!important on customizable select button
The HTML spec says that this button must always be inert and doesn't
provide a way to un-inert it. Authors have found that accidentally
removing inertness via CSS all:unset is unexpected.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
The WPT PR for this CL has been merged upstream! https://github.com/web-platform-tests/wpt/pull/58913
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |