pcowans a écrit : > I'm a little limited by difficulty of debugging in Internet Explorer, > but the result is that a listener attached to the dom:loaded event > sometimes triggers the dreaded 'operation aborted' error in IE 6 and > 7, leading me to suggest that it's not reliably executed after the DOM > is fully loaded. The code in question is part of a plug-in for third > party sites, so has to work around other people's code which may be > poorly written and may change after deployment.
Actually, whenever I had "operation aborted" on IE, it meant I had some inline script that tried to update a part of the DOM while not residing immediately under <body>. Google it, you'll find plenty. I never had any with external script bound unobtrusively, though… > Looking through the code I notice that the strategy taken to implement > dom:loaded in IE has essentially been rewitten since 1.6.0.2, and > other forum posts imply that the problems I'm facing are a known > issue. Ah, indeed. To prevent double-triggering and stuff. > Great - hopefully it'll be available before I need to ship this > code... Probably :-) -- Christophe Porteneuve aka TDD [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
