Search

No W3C DOM Event Listeners by steve_webdev

Active

62
Sign in to vote
2
Sign in to vote
Sign in
 to vote
Type: Bug
ID: 333958
Opened: 3/21/2008 5:08:58 PM
Access Restriction: Public
Duplicates: 355795
2
Workaround(s)
17
User(s) can reproduce this bug
See external ref here:

http://webbugtrack.blogspot.com/2008/03/bug-126-no-w3c-dom-level-2-event.html
Details (expand)

Please verify that this issue occurs in Internet Explorer 8 RTW. Click here for more information.

1. What seems to be the problem? Click here for more information.
There is a standards issue in Internet Explorer.

2. What area did the issue occur in? Click here for more information.
----Script Errors and Object Model

3. What language of your browser's frame? Click here for more information.
English

3a. What is your language preference order? Click here for more information.
 
 

Please try to reproduce this issue in No Add-ons mode and answer the following 2 questions. You can find the No Add-ons shortcut under All Programs > Accessories > System Tools > Internet Explorer (No Add-ons).  Click here for more information.


4.  What was the result of the issue after trying it in No Add-ons mode?
The issue reproduces in No Add-ons mode

5. If running in No Add-ons mode solves your issue, what kind of Add-ons are you using?
 

5a. If Other, then please list the add-on:
 


6. How often does this happen? Click here for more information.
Always Happens

7. What Operating System are you running? Click here for more information.
Windows XP SP3

8. Have you ever seen this problem before in Internet Explorer? Click here for more information.
This happens in IE6

9. Where does this occur?  Click here for more information.
Both

9a. Please provide the URL of the internet application being used.
 


10. Please list the reproduction steps. Click here for more information.
Try to use the standard event listeners that all other browsers (and the W3C) support

11. What are the expected results? Click here for more information.
Should be able to add W3C Standard event listeners

12. What are the actual results? Click here for more information.
Methods undefined.
File Attachments
0 attachments
Sign in to post a comment.
Posted by jeff_schiller on 4/10/2008 at 2:41 PM
Please support W3C DOM Event Listeners in IE8.
Posted by Microsoft on 4/11/2008 at 4:12 PM
Thank you for this feedback.

This is an expected behavior. IE currently does not have support for this W3C DOM Event Listener (addEventListener). We do appreciate your feedback on this issue and we will consider this for the future release of IE.

Best regards,

The IE Team.
Posted by steve_webdev on 4/12/2008 at 1:29 PM
You need a status for "Closed - We can't do right now, but yes, this is a bug that we will fix in the next version"

"By Design" sounds a lot like "We don't care about standards", for something that is obviously a bug.
Posted by steve_webdev on 11/28/2008 at 10:12 AM
Please reset the status to postponed.
Posted by steve_webdev on 4/21/2009 at 12:56 PM
re-opening issue for fixing in IE9 release
Posted by ShadowChaser on 5/4/2009 at 3:14 PM
I was just about to add a feature request for this. One of my top requests for the next version of IE is DOM Level 3 event support (ie/ addEventListener). The biggest "gap" between the browsers right now is DOM event handling. Put me down as a vote :)
Posted by t22harris on 8/18/2009 at 10:44 AM
Having two different event architectures to support sure is a hardship on the development community. What is the strategic purpose of not following the W3C standard? This is causing a ton of animosity amongst WEB developers. Please support W3C DOM Event Listeners in the future.
Posted by Daniel Smith on 9/1/2009 at 3:34 AM
I really hope this high up the priority list of IE9. I wish things like this could be addressed in a service pack for previous versions though. Even once issues such as this are addressed, the pain lives on years to come as support for older versions has to be maintained.
Posted by Sirisian on 11/30/2009 at 11:44 PM
Opened 3/21/2008? I wasn't going to say anything since I saw this a long time ago, but why hasn't this been fixed? I thought maybe this would be fixed in IE7. I waited for IE8, but I see that supporting attachEvent seems to be some kind of a goal against DOM? You know if you just support DOM Level 3 100% this would help everyone especially developers. It's not like attachEvent is going to win. It's a horrible name for a function especially in ECMAscript terms. You'll notice even in actionscript addEventListener is used.

Maybe I have a differing opinion but lets say hypothetically you released a browser or a patch that supports DOM 100%. If you made addEventListener work then all of those if (element.addEventListener) things would just use DOM. Slowly over time everyone would erase the ifs and it would turn into having one line adding the events. This can't possibly hurt your marketshare. Most users won't even realize it. However, every developer will thank you.
© 2010 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement