Assegnate 5 su 5 stelle

di Nizaury il Luglio 4, 2015 ·

Thank you.

After changing "extensions.fireie.currentTheme" parameter's value in about:config to the specified below, I was able to use the classic icons with FireIE without loosing signature.

{"id":"ietabtheme","fxURL":"http://ietab.googlecode.com/svn-history/trunk/src/extension/chrome/skin/ietab-engine-fx.png","ieURL":"http://ietab.googlecode.com/svn-history/trunk/src/extension/chrome/skin/ietab-engine-ie.png","textcolor":""}

or locale:

{"id":"ietabtheme","fxURL":"file:///D:/FireIEIcons/ietab-engine-fx.png","ieURL":"file:///D:/FireIEIcons/ietab-engine-ie.png","textcolor":""}

Best regards to author for this solution.

Questa recensione riguarda una versione precedente (0.4.5.2) del componente aggiuntivo. 

Assegnate 5 su 5 stelle

di Nizaury il Luglio 4, 2015 ·

After disabling multi-process, the addon start working in Firefox Developer Edition 41.0a2!!!

http://fireie.org/en/skins - not working, so please, could you add to the extension classic icons of IE and Firefox, or write the site? where I can get them.

Questa recensione riguarda una versione precedente (0.4.5.2) del componente aggiuntivo. 

di patwonder (Sviluppatore) il Luglio 4, 2015 ·

I'm sorry but fireie.org is currently down due to malicious attacks.

Before the site is up again, you can manually edit the about:config entry extensions.fireie.currentTheme to specify custom engine icon URLs for Firefox and IE engines. Don't forget to also change the id field to make Fire IE ignore the icon cache. If you have any questions, feel free to contact hi@yxl.name or patrick@fireie.org.

Assegnate 2 su 5 stelle

di Nizaury il Luglio 4, 2015 ·

Not working in Firefox Developer Edition 41.0a2 (2015-07-03).

Questa recensione riguarda una versione precedente (0.4.5.2) del componente aggiuntivo. 

di patwonder (Sviluppatore) il Luglio 4, 2015 ·

This is because Nightly purposely disabled plugin loading in the main process. See https://github.com/yxl/Fire-IE/issues/128#issuecomment-100589782 for details.

For now, the only workaround is disabling e10s (multi-process firefox) feature in Nightly settings.