Thanks Stefan. I was having that issue too. I re-enabled NPAPI and voila! I
back on track! Kudos!
On Monday, April 20, 2015 at 10:25:52 AM UTC, Stefan Bylund wrote:
I also noticed this yesterday.
The GWT Developer Plugin requires NPAPI, which was disabled in Chrome
version 42.
It is
I also noticed this yesterday.
The GWT Developer Plugin requires NPAPI, which was disabled in Chrome
version 42.
It is possible to temporarily re-enable it again using the URL
chrome://flags/#enable-npapi
Evidently, that option will disappear in Chrome version 45...
--
You received this
On Monday, April 20, 2015 at 12:34:08 AM UTC+2, Anderson Vasconcelos Pires
wrote:
This problem is happening with me too. Should we give up of GWT?
Obviously not! “Just” update to 2.7 and use SuperDevMode.
(SuperDevMode can be used since 2.5, but is really *usable* since 2.7)
I must say I
This problem is happening with me too. Should we give up of GWT?
Em sexta-feira, 17 de abril de 2015 12:17:44 UTC-3, Thomas Broyer escreveu:
On Friday, April 17, 2015 at 5:12:09 PM UTC+2, Chad Baker wrote:
I've been working with this plugin, using Dev Mode Classic for several
weeks without
Dear
I happend this time . so I try to use firefox 2.6.
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/26.0/win32/
so I can use dev mode.
I hope that the corresponding plug-in chrome as soon as possible
2015年4月18日土曜日 0時12分09秒 UTC+9 Chad Baker:
I've been working with this plugin,
I've been working with this plugin, using Dev Mode Classic for several
weeks without issues. All of a sudden, this morning, it now continually
prompts me to install the plugin, even though it already has been. I have
rebooted, uninstalled/re-installed first the plugin, then Chrome itself. Is
On Friday, April 17, 2015 at 5:12:09 PM UTC+2, Chad Baker wrote:
I've been working with this plugin, using Dev Mode Classic for several
weeks without issues. All of a sudden, this morning, it now continually
prompts me to install the plugin, even though it already has been. I have
