6598 2006-01-16 15:24:58 -0800 Should support IE Node methods attachEvent and detachEvents 2022-06-14 16:41:00 -0700 1 1 1 Unclassified WebKit DOM 420+ Mac OS X 10.4 RESOLVED WONTFIX InRadar P2 Normal --- 1 andersca webkit-unassigned aestes ahmad.saleem792 annevk ap bdakin ddkilzer ian rjiang rniwa zalan oldest_to_newest 28624 0 andersca 2006-01-16 15:24:58 -0800 Documentation at http://msdn.microsoft.com/workshop/author/dhtml/reference/methods/attachevent.asp http://msdn.microsoft.com/workshop/author/dhtml/reference/methods/detachevent.asp 28975 1 jhaygood 2006-01-20 05:45:07 -0800 A shared implementation with the W3C methods is possible. attatchEvent("onload",functionRef) is 100% equivalent to addEventListener ("load",functionRef,false) for instance 40160 2 ap 2006-04-22 09:16:24 -0700 Fixing this would fix bug 8534. 41901 3 ap 2006-05-10 13:40:34 -0700 <http://www.quirksmode.org/blog/archives/2005/08/addevent_consid.html>: "addEventListener and attachEvent should not be considered equal". This talks about the meaning of "this" keyword; looking at the documentation, the bubbling/canceling traits of similar IE and W3C events are also different. 44622 4 andersca 2006-06-04 09:48:01 -0700 We don't need to implement attachEvent and detachEvent in order to support live.com or start.com since the Mozilla compat layer is used which provides implementations of those functions 44648 5 hyatt 2006-06-04 11:33:44 -0700 This is one of those areas I'm nervous about supporting. 44649 6 hyatt 2006-06-04 11:34:29 -0700 If we added support for this, there are sites that would take us down the IE event handling code path. I'd rather wait to see if this is a real-world problem before adding support for it. 22746 7 jhaygood 2007-02-19 20:16:36 -0800 Couldn't this take the same approach as the hidden document.all support? Support it if its used, but not if its tested for directly: site does window.attachEvent("load",function); // Works site does if( window.attachEvent ) window.attachEvent("load",function); // Doesn't, since window.attachEvent is "hidden". 1838 8 fishd 2007-08-20 19:47:48 -0700 here's a real website (popular in the alexa rankings) that depends on attachEvent: http://house.vnet.cn granted, it uses attachEvent to scroll some advertisements as you scroll the page! 1833 9 mjs 2007-08-20 21:31:28 -0700 Well noted. Should we have a keyword to mark bugs that affect sites which are popular in the Alexa rankings? Also, is there any way to quantify the risk of sites giving us the IE-compatibility event handling code path that Hyatt mentioned? I would hope most sites would use addEventListener in preference to attachEvent when both are available, but it's hard to be certain. As a side note, I believe Opera supports the IE event handling methods. 57067 10 ap 2007-09-26 07:01:32 -0700 (In reply to comment #9) > Also, is there any way to quantify the risk of sites giving us the > IE-compatibility event handling code path that Hyatt mentioned? It seems that testing for attachEvent is a very common way to detect IE, so it clearly needs to be invisible if implemented. See, for example, <http://dev.rubyonrails.org/ticket/6800>. 62166 11 ddkilzer 2007-11-24 05:20:50 -0800 The left navigation panel of the MSDN site requires attachEvent/detachEvent: http://msdn2.microsoft.com/en-us/library/ms536694.aspx Because Firefox implements these DOM methods, the left nav panel works when this page is loaded on it. See the JavaScript in this file as well: http://msdn2.microsoft.com/App_scripts/ssmoz.js 62387 12 ian 2007-11-26 13:05:29 -0800 I don't understand the last comment -- Firefox doesn't support attachEvent(), and both Safari and Firefox are given attachEvent proxies in the aforementioned compat layer. 62389 13 ddkilzer 2007-11-26 13:09:33 -0800 (In reply to comment #12) > I don't understand the last comment -- Firefox doesn't support attachEvent(), > and both Safari and Firefox are given attachEvent proxies in the aforementioned > compat layer. Perhaps the compat layer is not being activated with Safari 3, then. Sorry...didn't look very deeply into the JavaScript code. 62394 14 ddkilzer 2007-11-26 13:48:11 -0800 (In reply to comment #13) > (In reply to comment #12) > > I don't understand the last comment -- Firefox doesn't support attachEvent(), > > and both Safari and Firefox are given attachEvent proxies in the aforementioned > > compat layer. > > Perhaps the compat layer is not being activated with Safari 3, then. > Sorry...didn't look very deeply into the JavaScript code. And this would be Bug 13546! 68241 15 rjiang 2008-01-25 17:12:47 -0800 Another example of site using this: https://personal.bank.ecitic.com:444/js/menu4.js This is top 7th bank in China. Log in with IE from https://personal.bank.ecitic.com:444 (you need an account though) 286345 16 aestes 2010-09-28 10:27:20 -0700 <rdar://problem/7867748> 286778 17 annevk 2010-09-29 02:04:49 -0700 (In reply to comment #9) > As a side note, I believe Opera supports the IE event handling methods. We are in the process of removing support for these. 1875895 18 ahmad.saleem792 2022-06-14 15:29:16 -0700 Can this bug be closed since even IE11 dropped the support for "attachEvent" in 2013 (release date) and now IE11 is also getting marked as EOL / EOS tomorrow (based on my timezone). https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/aa703974(v=vs.85) 1875908 19 rniwa 2022-06-14 16:41:00 -0700 Yeah, this is "won't fix"