Hi Kevin, To answer a few questions you raised:
1) It does seem to be the defer attribute which causes the issue. If the replacement script is triggered from window.onload, it works fine. 2) Clearing the browser's history seems to have no effect. However, if you clear your cache and then restart your browser, the problem is solved. I've experimented with delaying the replacement script using setTimeout. So, the deferred script sets up a delay, and then the replacement script is executed after that delay. If you set the delay long enough, the problem is solved - no "click to activate". I haven't quite narrowed down how long the delay needs to be exactly, but it does seem to point to some issue in the timing of events. Perhaps there is a magic sweet spot between the execution of deferred scripts and window.onload when elements can be inserted into the document without "click to activate". There also seems to be a relationship between the length of delay necessary versus the filesize of the SWF being inserted into the document. Which makes no sense to me, since SWFs stream. I do kind of feel like we should take this off list if we get into a lot of JavaScript - even though it relates to Flash in this context. Thoughts? -tom -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Newman Sent: Wednesday, June 14, 2006 1:03 PM To: Flashcoders mailing list Subject: Re: [Flashcoders] Eolas "fix" and backspace key flash bug Hello, I have not been able to reproduce that problem with IE 7 beta, but I have found that it occasionally stalls out after the files have been cleared from the cache (though not if this is the first time to visit the page, then it seems to work fine - maybe if all history is cleared and not just the cache it solves the problem?). I think the defer attribute on the script my be causing this - I have had some issues with using this method as an ondomcomplete event mimicker, and I'm not sure it always works (it definitely does not under IE 5.5 on Windows 98 that I'm running in VMware - it's the standalone install, which might be the problem). Do you have the same problem if you are running this script from onload instead of using the deferred script? If so, then a possible fix might be to use ondocumentready instead, and just fix the objects that are available at each stage of ondocument ready (I have never used that, so I'm not sure it would work, but it might be worth a try, if this is an onload problem). If that is not the problem and/or that solution doesn't work, it might be possible to add the replacement script the each individual object tag's onload, so that the replacement doesn't happen until we know that the specific object has been loaded (though I'm not sure they are loading if you set the display to none, and if they are, then you get the double loading issue). Setting these onload properties could be done during the stages of ondocumentready (or if the deferred script is actually working, we could just use that). I will do some testing on these tricks, and see what I can come up with, but I probably will not be able to get to it any time soon - its quite busy around here. :-) BTW, I have no problem discussing this stuff in the mailing list, if it isn't too OT. Thanks, Kevin N. Tom Lee wrote: > Kevin, > > I just tried out your patentmagic demo, and found that it suffers from the > same problem I have faced in my own attempts. If you empty your cache and > then reload the page, the Active X control does require activation. (I have > verified this on 3 individual PCs). I blogged about the problem at > http://tom-lee.blogspot.com/2006/06/eolas-workaround-fails-if-triggered.html > . The post contains a test page to verify. Perhaps we can join forces and > figure out what the hell's going on with this? I'd be happy to work with > you off-list if you prefer. > > -tom > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Newman > Sent: Tuesday, June 13, 2006 3:49 PM > To: Flashcoders mailing list > Subject: Re: [Flashcoders] Eolas "fix" and backspace key flash bug > > Is the problem that you can't run Javascript at all, or that you need to > put the embed code in html instead of javascript? > > You could use this patent fix: > http://www.unfocus.com/projects/patentmagic/ > > It still relies on scripting being enabled (so you'd still have this > problem for anyone that doesn't have JS enabled - if they don't have JS > enabled, they probably don't have ActiveX enable either though), but you > can at least use your html markup to embed the flash movie. > > Kevin N. > > > Alec Matusis wrote: > >> I have to embed flash applets into web pages directly, without Javascript >> Eolas "workaround". The users therefore have to "click to activate" the >> flash movie in IE. >> >> After that, the Flash movie properly receives the text input, EXCEPT for >> Backspace and Tab keys. Pressing Backspace has an action of "Back" button >> > in > >> the browser, it takes a user back one page. Pressing Tab moves the focus >> into another object in the browser. >> >> So it looks like when the control is "activated" , the Flash receives only >> > a > >> PARTIAL focus: it accepts all text input except Backspace and Tab. When >> > you > >> click on Flash the second time, it receives full focus, and Backspace and >> Tab function properly. >> >> Can anyone explain this behavior? Is this an IE bug? >> >> >> > > _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
