RESOLVED CONFIGURATION CHANGED15696
Safari and Firefox differ in event handling behavior when placing <div> elements inside <button> elements 
https://bugs.webkit.org/show_bug.cgi?id=15696
Summary Safari and Firefox differ in event handling behavior when placing <div> eleme...
Kevin Decker
Reported 2007-10-25 16:55:12 PDT
Safari and Firefox differ in event handling behavior when placing <div> elements inside <button> elements. * STEPS TO REPRODUCE 1. Open attached test case and click within the red block. * RESULTS In Firefox, the button gets the event. In Safari both the div *and* button receive events.
Attachments
test case (123 bytes, text/html)
2007-10-25 16:55 PDT, Kevin Decker 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Kevin Decker
Comment 1 2007-10-25 16:55:39 PDT
Created attachment 16868 [details] test case
Gabriel Humeniuc
Comment 2 2009-05-09 10:22:51 PDT
The comportament of Firefox is similar in Internet Explorer 6, and Opera 9.63 whitch I presume it is correct one.
Alexey Proskuryakov
Comment 3 2012-10-19 13:14:55 PDT
See also: bug 89041, bug 99712.
Ahmad Saleem
Comment 4 2022-08-07 15:15:03 PDT
I am able to reproduce this bug in Safari 15.6 on macOS 12.5 an it gives <div> and <button> events while Firefox Nightly 105 only does <button> event. While Chrome Canary 106 matches with Safari here. I am not sure on web-spec so I would leave the team to decide whether it is something which needs to be aligned with Firefox or Firefox need to change the behavior. Thanks!
Radar WebKit Bug Importer
Comment 5 2022-08-08 11:16:55 PDT
<rdar://problem/98330762>
Ahmad Saleem
Comment 6 2024-10-13 06:00:21 PDT
I just retested it after quite a while. *** Safari 18.1 Beta *** Clicked - dialog 'button' *** Chrome Canary 131 *** Clicked - dialog 'button' *** Firefox Nightly 133 *** Clicked - dialog 'button' ___ It seems that now all browsers are aligned and have same behavior. Something might be changed during last testing with Safari 15.6 and now. I am marking this as 'Configuration Changed', please reopen, if it is still reproducing or something tested wrong.
Note You need to log in before you can comment on or make changes to this bug.