To understand, is it to mimic the following Javascript snippet ?

var sss =
Components.classes["@mozilla.org/content/style-sheet-service;1"].getService(Components.interfaces.nsIStyleSheetService);
var ios =
Components.classes["@mozilla.org/network/io-service;1"].getService(Components.interfaces.nsIIOService);
var u = ios.newURI("chrome://flashblock/content/flashblock.css", null, null);
sss.loadAndRegisterSheet(u, sss.USER_SHEET);

Then, the problem is how to install all the relatives chromes (flashblock.css,
flash.xml, director.xml, ...), right ?

Right.

I tried replacing the chrome:// with corresponding file:// references; the css
was applied then but apparently the XBL bindings not. So we need to find a way
to register chrome.

Could it be possible to play with nsInstall::RegisterChrome method ?

http://lxr.mozilla.org/seamonkey/source/xpinstall/src/nsInstall.h

*** Bug 136060 has been marked as a duplicate of this bug. ***

http://live.gnome.org/Epiphany/FlashBlock is still messy, geeky and doesn't work most of the time.

Having a flashblock extension would definitely be nice.

Would be nice to have in line with http://blogs.gnome.org/xan/2012/10/03/on-advertisement-and-international-traveling/ , like Firefox's built-in (but disabled) "click_to_play" feature/setting for plugins such as Flash.

*** Bug 455504 has been marked as a duplicate of this bug. ***

Closing this bug as it concerns NPAPI plugins.

I insist that NPAPI plugins are still supported and used by epiphany, there's no reason to not fix the problems related to the plugins, only because one day we might use another window system.

The absence of a "click-to activate" feature is an almost prohibitive shortcoming which is a big obstacle for wider adoption of "GNOME Web".

(In reply to Joachim Frieben from comment #10)
> The absence of a "click-to activate" feature is an almost prohibitive
> shortcoming which is a big obstacle for wider adoption of "GNOME Web".

Given that you can't run any recent version of Flash in epiphany, I don't see how that could even be a shortcoming nowadays.

(In reply to Bastien Nocera from comment #11)
Interesting, I am currently using the latest Flash plugin version 11.2.202.632 both with epiphany 3.18.5 and epiphany 3.21.4.

(In reply to Joachim Frieben from comment #12)
> (In reply to Bastien Nocera from comment #11)
> Interesting, I am currently using the latest Flash plugin version
> 11.2.202.632 both with epiphany 3.18.5 and epiphany 3.21.4.

Unfortunately we're probably up to Flash version 20something now, Linux has been left behind.

Anyway, patches for click-to-play plugins are absolutely welcome; it probably doesn't require any changes in Epiphany, just in WebKit. I'm not personally interested in spending time on NPAPI myself as I think other issues are higher priorities, but I'll review any patches sent my way. (Some reasons for thinking this is low priority: Flash is the only plugin left that matters. It being proprietary, I won't install it. Mozilla and Google are both accelerating plans to kill it. Flash will never work in Wayland, and the non-Wayland case will soon not be very interesting to me anymore.)

(In reply to Joachim Frieben from comment #12)
> (In reply to Bastien Nocera from comment #11)
> Interesting, I am currently using the latest Flash plugin version
> 11.2.202.632 both with epiphany 3.18.5 and epiphany 3.21.4.

Current Chrome provided version is 22.0.0.192. You're running something full of security holes, in addition to the other problems mentioned by Michael.

(In reply to Bastien Nocera from comment #14)
> Current Chrome provided version is 22.0.0.192. You're running something full
> of security holes, in addition to the other problems mentioned by Michael.

(Adobe is actually releasing security fixes for Linux still. No denying that Flash is the most vulnerable software on your computer nevertheless... but that's what click-to-play is meant to mitigate, after all.)

Hm, this is really a WebKit issue. Nothing we can do about it in Epiphany.

Thanks for taking the time to report this.
This issue is most likely a bug in WebKit. Please report the bug to https://bugs.webkit.org/ including a link to this bug report and noting the version of WebKitGTK+ that you have installed. When reporting the WebKit bug, be sure to include the prefix '[GTK]' in the bug summary and select the 'WebKit Gtk' component.

This issue has been reported in WebKit's bugzilla as https://bugs.webkit.org/show_bug.cgi?id=167852.