"Click to activate this ​control&quo​t; It's GONE in SP1!

Yeah, they paid off the patent pirates.

I kindof liked it

Lloyd_Humph wrote:

I kindof liked it

It's optional. Anyway, on XP it's still there, just some flash controls seem to be able to override it.
I'd like to know how this overriding works.

Lloyd_Humph wrote:

I kindof liked it

You can't be serious...

Its a shame that this went on for 18 months and measures had to be taken by developers to circumvent it. There are other slight advantages to inject via JS with something like SWFObject still but it means that we have to keep using it whether we want to or not as there is 18 months of IE6 and IE7 out there that potentially does not have the re-fix t deal with and accommodate. Opera I believe have also decided to make their browser Eolas compliant too.

littleguru wrote:


You inject the control via javascript. That's how you need to work around the "patent". There was a problem on how the stuff was integrated (and activated) in the website. Via JavaScript that patent claim couldn't be endorsed and that's why injecting the flash via javascript works without the "Click to activate this control" thing.

Nope JS doesn't do the trick here in the way I would want it. In IE7 you have an option to choose wether (all) controls need activation click or not. This also goes for the media player and quicktime controls (whatever...). However, for the Flash controls, sometimes this so called security feature doesn't work at all. I tried to disassemble (yay, SWF decompilers rock) those flash files, but I couldn't really figure what did the trick, and always this flash control was embedded without DOM JS but directly with object tags and simple embed.
Also, injecting the flash with JS doen't always override the click me please to activate me stuff.

Dodo wrote:



littleguru wrote:  You inject the control via javascript. That's how you need to work around the "patent". There was a problem on how the stuff was integrated (and activated) in the website. Via JavaScript that patent claim couldn't be endorsed and that's why injecting the flash via javascript works without the "Click to activate this control" thing.

Nope JS doesn't do the trick here in the way I would want it. In IE7 you have an option to choose wether (all) controls need activation click or not. This also goes for the media player and quicktime controls (whatever...). However, for the Flash controls, sometimes this so called security feature doesn't work at all. I tried to disassemble (yay, SWF decompilers rock) those flash files, but I couldn't really figure what did the trick, and always this flash control was embedded without DOM JS but directly with object tags and simple embed.
Also, injecting the flash with JS doen't always override the click me please to activate me stuff.

Using SWFObject it doesn't require "click to activate". SWFObject is the defacto standard for embedding Flash on a page.

Read more bout SWFObject here

Custa1200 wrote:

Using SWFObject it doesn't require "click to activate". SWFObject is the defacto standard for embedding Flash on a page.

So you want to tell me if I turned on the 'click to activate' security option in IE7 for all ActiveX Controls, using JS to document.write the stuff into the DOM layer works around this?
I hope this doesn't work for WMP and other embedding... gonna test that now.

Dodo wrote:

So you want to tell me if I turned on the 'click to activate' security option in IE7 for all ActiveX Controls,

Just to be clear, this was never a security option. It exists purely to comply with the Eolas patent.

AndyC wrote:


Just to be clear, this was never a security option. It exists purely to comply with the Eolas patent.

Then tell me what do those options do?

Dodo wrote:



AndyC wrote:  Just to be clear, this was never a security option. It exists purely to comply with the Eolas patent.

Then tell me what do those options do?

Those are entirely separate from the Eolas thing (which wasn't optional), they remain and function as they did before.

I remember explicitely that Microsoft instantly openly posted the way around it (by using javascript injection)..

Again, the injection isn't a flaw, the activation isn't a security issue, its regarding the way components are automatically activated, its highly political more than anything, and its a great example of the shite Microsoft has to deal with..