996947 - GWT Developer plugin stopped working on Firefox

Status: RESOLVED WONTFIX

(Firefox Build System :: General, defect)

Description

[Mario Jauvin]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0 (Beta/Release)
Build ID: 20140314220517

Steps to reproduce:

Trying to use GWT plugin on Firefox 28


Actual results:

Message from Google saying GWT not supported on Firefox 25 and above


Expected results:

loaded the plugin

Comment 1

[Mario Jauvin]

See bug 920731 for details.

Comment 2

[Mario Jauvin]

I kind of understand the motivation for not exposing the JSAPI constants but this has caused GWT developer plugin to stop working in Firefox release 25 onwards.  Regardless of the issue with the exposing Firefox JSAPI, would:

1. it be possible for someone from Mozilla to communicate with GWT developpers and propose a solution that could be implemented?
2. it be possible to revert the change that caused the JS symbols to stopped being exported until such time as GWT developpers have implemented the solution proposed in 1.

I see that you have contacted Norton for their toolbar and you made provisions for helping Thunderbird for their transitions I am sure you should be able to do the same for the GWT user community that use Firefox who are currently SOL?

Comment 3

[Mario Jauvin]

Please do not mark this bug as duplicate of 920731.  920731 was about not exposing JS symbols to extensions.  This is about GWT not working on Firefox.

Comment 4

[Mario Jauvin]

See google issue for GWT plugin here:

https://code.google.com/p/google-web-toolkit/issues/detail?id=8553

Comment 5

[Mario Jauvin]

I have added a few interested party on the cc list.

Comment 6

[Leon]

Would it be possible for Mozilla to export the required C++ symbols in this upcoming developer release?
https://blog.mozilla.org/blog/2014/11/03/the-first-browser-dedicated-to-developers-is-coming/

So the GWT dev plugin could work again on this developer only version.

I know that people from Google seem to have given up on it and are recommending to use Super Dev mode. Still it's very nice to be able to debug from your own IDE.

Comment 7

[mtr]

(In reply to Leon from comment #6)
> Would it be possible for Mozilla to export the required C++ symbols in this
> upcoming developer release?
> https://blog.mozilla.org/blog/2014/11/03/the-first-browser-dedicated-to-
> developers-is-coming/
> 
> So the GWT dev plugin could work again on this developer only version.
> 
> I know that people from Google seem to have given up on it and are
> recommending to use Super Dev mode. Still it's very nice to be able to debug
> from your own IDE.

Yes please ! I would certainly expect that kind of debugging possibilities from "developer only version" of FF!

Comment 8

[Peter Clemons]

While I think Google and Mozilla should get their act together and allow developers to use their IDEs to develop for GWT using the release builds of FireFox, I love this suggestion as a reasonable "interim" compromise

...Mozilla, at least for DEV BUILDS, please export the FF symbols!

Comment 9

[Brian Slesinsky]

The GWT Dev Mode plugin for Firefox is no longer maintained. For this to make sense, someone would need to volunteer to maintain it.

(Google isn't going to do this; we've switched to Super Dev Mode.)

Comment 10

[Joe Walker [:jwalker]]

Can we enable the JS_ symbols in the Developer Edition as released on the 10th? No, sorry - it's too late for that.

I'm new to the GWT addon, but it seems that if Google are not supporting this any more and recommending Super Dev mode then that seems like the only long term option. It doesn't seem reasonable to have long term binary level backwards compatibility requirements from an unsupported add-on.