Discuss the 'click-to-activate' fix for IE6+ and Opera9+ (static publishing method) about swfobject HOT 6 CLOSED

For means of documentation, the current fix uses techniques from:
- http://www.sitepoint.com/article/activex-activation-issue-ie
-
http://www.thefutureoftheweb.com/blog/work-around-click-to-activate-and-use-this
-control
- http://www.howtocreate.co.uk/operaStuff/userjs/noclicktoactivate.js

However as noted above: These solutions have major drawbacks.

I did some additional research and tried a method like:
window.onload = function() {
  var obj = document.getElementById("myId");
  if (typeof document.fireEvent != "undefined" && typeof document.createEventObject
!= "undefined") {
    obj.focus();
    var e = document.createEventObject();
    e.ctrlKey = true;
    e.keyCode = 13; // return (32 for spacebar)
    document.fireEvent("onkeydown", e);
  }
};

Despite that the keydown event fires correctly, it isn't seen as a user event 
and the
'click-to-activate' mechanism remains.

This means that:

I have taken the fix out of the code for the next beta, because the cure seems 
to be
just as bad as the disease. So unless we find a better method later on (and I 
doubt
that) does the static publishing method not offer a solution for the
'click-to-activate' active content problem.

For those who want to avoid this mechanism, should use the dynamic publishing 
method.

Furthermore you can discuss how harmful this mechanism really is for the user
experience. It is also unclear if Microsoft will keep the mechanism inside IE 
now
they have settled the dispute with Eolas:
- http://blog.seattlepi.nwsource.com/microsoft/archives/120899.asp
- http://www.techmeme.com/070830/p62#a070830p62

[deleted comment]

Don't know if it helps, but here's script I wrote for my old pages.
It triggers onDom and works on IE6+ and Opera9+(9.5beta is another problem). 
Also it doesn't have IE flashvars issue like some other scripts, and it's few 
loops 
smaller.

you write "Also a document.onreadystatechange strategy doesn't seem to work..."

do you mean that the dean edwards et al "script defer" domloaded method you were
using does not trigger consistently? or that rewriting the <object>'s html at 
that
point is not reliable?

thanks!

Seems like this problem is going away on its own:
- 
http://blogs.msdn.com/ie/archive/2007/11/08/ie-automatic-component-activation-ch
anges-to-ie-
activex-update.aspx

@bunnyhero: I meant to write object.onreadystatechange, not
document.onreadystatechange. Sorry for the confusion.