[strager]

It does, though not with the same UI as the Java plugin: http://i.imgur.com/xHrRX.png

Clicking the puzzle piece shows a menu to "always allow" or to "enable all Flash applets on this page" (and a few other things).

I can see a more obtrusive/apparent UI being implemented if Firefox makes click-to-Flash default.

[mistercow]

That's not the same interface that I was referring to. I was talking about this: http://i.imgur.com/8lzif.png

[notatoad]

it's not the same appearance, but it's the same functionality.

[mistercow]

No it's not, because if the Flash object is invisible, it simply does not give you any way to enable them unless you go to the preferences and explicitly add an exception.

This was my entire point in the first place, if you look up at the beginning of the thread. For example, turn on click-to-play and then go to pandora.com. If Chrome treated Flash the same as Java, you would still be able to use pandora easily.

[notatoad]

read his post again. he's not talking about the click-to-play ui. there's a puzzle piece icon in the taskbar. clicking it displays a drop-down menu, and even if the flash is invisible you can choose the "enable flash on this page" option.

[mistercow]

Ah yes, I see now.

[albemuth]

A problem I found with Chrome's current implementation is on pages where you don't even know flash is being used, Google Translate and Soundcloud for example, after thinking the site was broken I remembered I had click-to-enable active.

[strager]

Indeed, this happens to me too. And I think this is why Mozilla will need to have a very good UI to tell the user how to fix a broken site (or just fix it for them e.g. through a crowd collective).