91463 2012-07-16 19:08:40 -0700 add support for beforescriptexecute/afterscriptexecute event 2019-02-06 21:56:13 -0800 1 1 1 Unclassified WebKit DOM 528+ (Nightly build) Unspecified Unspecified RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/multipage/scripting-1.html#the-script-element HTML5, InRadar, WebExposed P2 Normal --- 32934 1 syoichi webkit-unassigned ap ayg cdumez cris.bugzilla djkrose eric herbert00 joepeck kitit lquinn michael mike priston910423 rniwa sroussey tomme87 webkit-bug-importer webkit.bugzilla webkit zanetu oldest_to_newest 670899 0 syoichi 2012-07-16 19:08:40 -0700 > 2. Fire a simple event named beforescriptexecute that bubbles and is cancelable at the script element. > If the event is canceled, then abort these steps. > (snip) > 6. Fire a simple event named afterscriptexecute that bubbles (but is not cancelable) at the script element. http://www.whatwg.org/specs/web-apps/current-work/multipage/scripting-1.html#the-script-element 672627 1 ap 2012-07-18 12:32:59 -0700 Do other browsers support this? 673041 2 syoichi 2012-07-18 18:11:34 -0700 (In reply to comment #1) > Do other browsers support this? Yes, it's Firefox 4+(Gecko 2+). https://bugzilla.mozilla.org/show_bug.cgi?id=587931 https://developer.mozilla.org/en/DOM/element.onbeforescriptexecute https://developer.mozilla.org/en/DOM/element.onafterscriptexecute By the way, Opera's User JavaScript has BeforeScript/AfterScript event. http://www.opera.com/docs/userjs/specs/#BeforeScript http://www.opera.com/docs/userjs/specs/#AfterScript But, I'm not sure whether current Firefox's implementation follow HTML spec. related: http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-February/034629.html http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-May/035713.html 798007 3 zanetu 2012-12-28 15:38:47 -0800 I can confirm this bug with Chrome v23.0.1271.97 on 64-bit Debian Unstable. Both Iceweasel v10.0.11 and Opera v12.12 support "beforescriptexecute" whereas Chrome v23.0.1271.97 does not. 851827 4 webkit 2013-03-09 14:28:23 -0800 Just ran into this bug in Chrome 25.0.1364.97 [537.22 (@143379)]. Please add support to match firefox support and comply with the spec. 962269 5 tomme87 2013-12-21 13:36:51 -0800 Ran into this bug myself. Not having this functionality is very frustrating, specially when making userscripts. 995170 6 zanetu 2014-03-27 17:24:46 -0700 Now that beforeload, which used to be the only workaround, is no longer supported (https://code.google.com/p/chromium/issues/detail?id=333318), this bug appears more urgent than ever. :( 1123750 7 rniwa 2015-09-04 17:10:51 -0700 This is now covered by LayoutTests/http/tests/w3c/html/semantics/scripting-1/the-script-element/script-before-after-events.html 1123752 8 webkit-bug-importer 2015-09-04 17:12:03 -0700 <rdar://problem/22588270> 1124584 9 michael 2015-09-09 01:29:23 -0700 Advertisers have started to bypass adblockers by using special inline scripts. Recent approaches for analyzing and blocking these scripts (e.g. https://openuserjs.org/scripts/schwarztee/AdDefend_Klatsche/source) won't work in webkit unless these events are implemented! 1134576 10 kitit 2015-10-19 07:57:54 -0700 Come on guys, Firefox already implemented this, you didn't. Therefore WebKit browsers fail certain HTML5 tests, like this one: http://www.w3c-test.org/html/semantics/scripting-1/the-script-element/script-before-after-events.html Firefox passes all these tests. I thought WebKit is all about supporting standards like HTML5? 1134580 11 herbert00 2015-10-19 08:26:45 -0700 This is very important functionality. The developers of AdBlock Plus (one of the most installed addons) need this to implement a new feature: https://issues.adblockplus.org/ticket/3207 But they can't because Chromium developers refuse to implement a feature that is officially part of the W3C HTML5 standard. 1158852 12 cris.bugzilla 2016-01-26 10:15:28 -0800 A polyfill : https://github.com/dosaygo/open-0/tree/master/script-events 1337419 13 ayg 2017-08-10 08:10:57 -0700 This is no longer in the spec, so if you actually want to implement it, you should probably get it re-added to the spec first. 1503334 14 lforschler 2019-02-06 09:19:12 -0800 Mass move bugs into the DOM component. 1503631 15 rniwa 2019-02-06 21:56:13 -0800 We're not going to implement this non-standard event, which has been removed from the spec.