Joey Arhar
Joey Arhar
In the interest of making consistent behavior for disabled form controls which do or don't have child elements, I think these are our options: - Option A: Always propagate click...
I added a UseCounter: - https://chromium-review.googlesource.com/c/chromium/src/+/3754929 - https://chromestatus.com/metrics/feature/timeline/popularity/4296 It should reach stable starting on August 30th, so hopefully by September 6th or 13th we will have some data. If by...
It looks like the UseCounter from my last comment is at 0.1%, which isn't a huge number but it does go above the threshold for knowing that we can safely...
I am going to try shipping the firefox behavior of propagating events up to disabled form controls but not to their parent elements. Let's see how far I can get.
I filed an intent to ship in chromium: https://groups.google.com/a/chromium.org/g/blink-dev/c/9i0H0J0BzE4
Woohoo! Thanks @saschanaz ! I am going to slowly enable the new behavior in chrome starting with chrome 110
> If one removes a popup from dom (that triggers async hide) and then adds it back and opens the popup, there will be a sync show event, right? And...
This would be closed by https://github.com/whatwg/html/pull/9462 right?
I'm not aware of any reason why this can't be changed, but I'm also not an expert on the dialog element in the first place. As I said in [this...
> The reason we have been historically opposed to this in Chrome is that it is contrary to how native dialogs behave. (That is, the current specification matches native dialogs,...