While I agree to some point, no JavaScript library event implementation is perfect, and it will never be able to truly compete with native support. Most definitely! While the scope of this issue might not match the version targeting thing, it's still very important that everyone spread the word and express their opinion, blog about it etc.
The W3C could have used the same implementation but no, they had to add event capturing which hardly ever gets used by anyone. Also you seem to have the common misconception that the evt argument in your attachEvent example is not going be set to the event object, which is not the case.
Microsoft is in that group too, so I'm sure it was discussed and then disregarded in unity. On the contrary, I'm afraid it is. I guess it's not such a trivial thing to do. It must be needing some heavy modifications to the JS engine, which would introduce many bugs, which would delay IE8, which is not acceptable. JS libraries are fixing the problem, and more eg: memory leaks. The problem is such an issue is what makes IE to suck to developers.
But who cares? Users will be happy — and developers will continue to rely on libraries to write JS. The problem is, though, that it will have to be fixed, sooner or later. When will it be addressed? It's certainly acceptable to me … even with the first birthday of IE7 over and done with, we're still waiting for IE6 numbers to drop. But let's face it, after so many years of blatant disregard for the development community, it should come as no surprise to anyone that Microsoft cares very little for the enormous financial burden they place upon us developers, ISV's, businesses by continuing to publish half-arsed software.
With that in mind, it is much harder to forgive them for letting this serious bug go. They're not going to change it, you know. Please navigate to this page using a different web browser. Given Firefox continuous marketing gain, together with Safari, Chrome and the WebKit rendering engine's increasing share in general, I think that, sooner or later, Microsoft will have to fix it.
This is essentially Microsoft moving at their usual, natural pace. They move on their own time and don't care if they're sitting on anyone else's. Internet Explorer 7 is an improvement over IE6, but only so much as to be an aggravating umpteenth browser to support, and not enough to make much of a marked improvement.
They make mind boggling decisions that damn near bring me to tears. Microsoft has no incentive to do anything the way anyone but Microsoft wants them to be done.
This is why monopolies are such a big deal…. I would like to think we're in a time where Microsoft finally has something on the line. They have lost tremendous amounts of market share to Firefox and Safari to a lesser extent , plus we may well have a strong new competitor from Google, yet it still seems like they're waiting until the bullet casings hit the floor before they decide to move.
Internet Explorer 8 has consistently promised to be the beginning of Microsoft's rebirth as a friendlier, more responsible company. I have been enamored with the thought that has been put into the Windows 7 UI and how constructive they have been of their criticisms of Vista's weak points, but it always seems like there's a catch. For every success Microsoft has, there's another whopping failure, and IE8 has epitomized this.
It wasn't until pressure was put on it that it decided to release IE8 with Standards mode enabled, and it only does enough to pass the Acid2 test, and fails Acid3 horribly. You can say what you want about these tests, but IE8 thus far mangles my sites. It seems more like an evolutionary upgrade to IE7; they get a little closer to compliance, but not enough to make this a worthwhile release.
This is Microsoft's opportunity to steal back what they're losing, and they're just doing what they do best: waiting for the last nail in the coffin. Someone needs to light a damn fire under their ass.
How loathable the MS attitude is in this case, they also paved the way for a bunch of fantastic frameworks. These address far more issues beyond pure IE problems, and brought us things like easy to implement tabboxinterfaces and the like. Absolutely, they really need to ix things as soon as possible before they're overun by their competitors. But just imagine of all that hard work and creativity had been put into something new and better instead of fixing bugs?
What exactly is it that could be done on the client side that would be of great benefit for users that cannot be done now with the workarounds for the IE event model that already exist?
Second, what would greatly improve the end user experience is that instead of workarounds, which will always be a performance as well as code risk, it would work the way it should right out of the box. Anyway, thanks.
Podcast Explaining the semiconductor shortage, and how it might end. Does ES6 make JavaScript frameworks obsolete? Featured on Meta. Now live: A fully responsive profile.
Linked 7. Related Hot Network Questions. Stack Overflow works best with JavaScript enabled. Accept all cookies Customize settings. Eduardo Sousa. Only authorized users can answer the question. Please sign in first, or register a free account. Not the answer you're looking for? Browse other questions tagged : javascript. So ok, I waited.
Great, finally, I thought, Internet Explorer is catching up to the rest of the world. We've been wrong I guess. They just added some high-end features to fool us. Basically, you use a method called addEventListener to add an event to an element, like this:.
If you're doing your own event handling in plain javascript, then you probably already have a cross browser routine for setting event handlers. You can put the abstraction in that function. Here's one that I use that mimics the jQuery functionality if the event handler returns false, then both stopPropagation and preventDefault are triggered.
You can obviously modify it however you want it to behave:,For those of you wanting to maximise your javascript code reuse without refactoring, I've managed to get a version working that declares a log of the form console. This will cause your JavaScript to yield to the browser so it can perform its rendering, respond to user input and so on , but without forcing it to wait a certain amount of time:,Note that I have tried to define a vararg version log taking multiple parameters but I couldn't get this to work correctly across the framework api.
0コメント