Bugzilla

(In reply to Karl Dubost💡 :karlcow from comment #2)
> * Testcase 2 is not working anywhere.

This hasn't changed since the bug was filed -- as noted in the attachment-title, it only ever worked in EdgeHTML (which is no longer relevant).

> * testcase 1 is working only in Safari Release 136 (Safari 15.4, WebKit 17613.1.9.2)

Interesting. It used to work in Chrome; I just bisected old versions and it seems that it still worked in Chrome 75, and stopped working in Chrome 76.  Not sure if that was due to a bugfix or a regression.

I don't really know what's going on or why it would make sense to eat pointer events here, but maybe we don't need to worry about this, given that we're relatively interoperable at this point? (and maybe there's a subtle reason that the interoperable but broken-feeling behavior is correct?)

Note that testcase 2 (where all modern browsers agree) is the same as testcase 1, except that testcase 1's border on the span has been removed in testcase 2. I don't see any reason why that border's presence/absence should make a difference for pointer events...  So it could be that Safari just happens to get lucky with the border present (in testcase 1) but really the interoperable behavior on testcase 2 is correct?

Anyway, I think we can easily downgrade this to lowest-priority. I'm tempted to close it except the behavior still feels broken, even if it's interoperable, and I'd kinda like to understand why it's correct before closing it. :)

(In reply to Karl Dubost💡 :karlcow from comment #2)
> * Testcase 2 is not working anywhere.

This fact hasn't changed since the bug was filed -- as noted in the attachment-title, it only ever worked in EdgeHTML (which is no longer relevant).

> * testcase 1 is working only in Safari Release 136 (Safari 15.4, WebKit 17613.1.9.2)

Interesting. It used to work in Chrome; I just bisected old versions and it seems that it still worked in Chrome 75, and stopped working in Chrome 76.  Not sure if that was due to a bugfix or a regression.

I don't really know what's going on or why it would make sense to eat pointer events here, but maybe we don't need to worry about this, given that we're relatively interoperable at this point? (and maybe there's a subtle reason that the interoperable but broken-feeling behavior is correct?)

Note that testcase 2 (where all modern browsers agree) is the same as testcase 1, except that testcase 1's border on the span has been removed in testcase 2. I don't see any reason why that border's presence/absence should make a difference for pointer events...  So it could be that Safari just happens to get lucky with the border present (in testcase 1) but really the interoperable behavior on testcase 2 is correct?

Anyway, I think we can easily downgrade this to lowest-priority. I'm tempted to close it except the behavior still feels broken, even if it's interoperable, and I'd kinda like to understand why it's correct before closing it. :)