Update Chrome to 10.0.612.1 does not work with either 2.1.0 or 2.1.1

[alanmechy]

Hi

I hope someone can explain this to me - it looks like the latest
version of Chrome doesn't work with GWT.

Chrome updated itself to 10.0.612.1 and immediately my project fails
to load:


com.google.gwt.dev.shell.HostedModeException: Something other than a
boolean was returned from JSNI method
'@com.google.gwt.user.client.impl.HistoryImplTimer::init()': JS value
of type JavaScript object(1), expected boolean
at com.google.gwt.dev.shell.JsValueGlue.get(JsValueGlue.java:100)
at
com.google.gwt.dev.shell.ModuleSpace.invokeNativeBoolean(ModuleSpace.java:
186)
at
com.google.gwt.dev.shell.JavaScriptHost.invokeNativeBoolean(JavaScriptHost.java:
35)
at
com.google.gwt.user.client.impl.HistoryImplTimer.init(HistoryImplTimer.java)
at com.google.gwt.user.client.History.<clinit>(History.java:63)
at
com.mechnicality.mollycore.client.HistoryWrapper.addValueChangeHandler(HistoryWrapper.java:
22)
at
com.mechnicality.mollyweb.client.MollyGWTApp.bind(MollyGWTApp.java:
276)


Which appears to relate to:

public class History {

private static HistoryImpl impl;

static {
impl = GWT.create(HistoryImpl.class);
if (!impl.init()) {
// Set impl to null as a flag to no-op future calls.
impl = null;

// Tell the user.
GWT.log("Unable to initialize the history subsystem; did you "
+ "include the history frame in your host page? Try "
+ "<iframe src=\"javascript:''\" id='__gwt_historyFrame' "
+ "style='position:absolute;width:0;height:0;border:0'>"
+ "</iframe>");
}
}

and the init() method is:

public native boolean init() /*-{
var token = '';

// Get the initial token from the url's hash component.
var hash = $wnd.location.hash;
if (hash.length > 0) {
token =
this.@com.google.gwt.user.client.impl.HistoryImpl::decodeFragment(Ljava/
lang/String;)(hash.substring(1));
}

@com.google.gwt.user.client.impl.HistoryImpl::setToken(Ljava/lang/
String;)(token);

var historyImpl = this;
$wnd.onhashchange = $entry(function() {
var token = '', hash = $wnd.location.hash;
if (hash.length > 0) {
token =
historyImpl.@com.google.gwt.user.client.impl.HistoryImpl::decodeFragment(Ljava/
lang/String;)(hash.substring(1));
}


historyImpl.@com.google.gwt.user.client.impl.HistoryImpl::newItemOnEvent(Ljava/
lang/String;)(token);
});

return true;
}-*/;


I tried updating from 2.1.0 to 2.1.1 and that makes no difference.

Regards

Alan

[Jim Douglas]

I see the same failure here.

It looks like Chrome dev version 10.0.612.1 breaks GWT DevMode, but
production mode seems to work ok.

http://code.google.com/p/google-web-toolkit/issues/detail?id=5778

FWIW, this appears to be a Chrome issue (as opposed to WebKit). The
problem does not occur in the 17 December nightly build of WebKit
(Version 5.0.3 (6533.19.4, r74228)).

On Dec 18, 2:10 pm, alanmechy <a...@mechnicality.com> wrote:
> Hi
>
> I hope someone can explain this to me - it looks like the latest
> version of Chrome doesn't work with GWT.
>
> Chrome updated itself to 10.0.612.1 and immediately my project fails
> to load:
>
> com.google.gwt.dev.shell.HostedModeException: Something other than a
> boolean was returned from JSNI method

> '...@com.google.gwt.user.client.impl.HistoryImplTimer::init()': JS value

> th...@com.google.gwt.user.client.impl.HistoryImpl::decodeFragment(Ljava/

> lang/String;)(hash.substring(1));
>     }
>
>     @com.google.gwt.user.client.impl.HistoryImpl::setToken(Ljava/lang/
> String;)(token);
>
>     var historyImpl = this;
>     $wnd.onhashchange = $entry(function() {
>       var token = '', hash = $wnd.location.hash;
>       if (hash.length > 0) {
>         token =

> historyIm...@com.google.gwt.user.client.impl.HistoryImpl::decodeFragment(Ljava/
> lang/String;)(hash.substring(1));
>       }
>
> historyIm...@com.google.gwt.user.client.impl.HistoryImpl::newItemOnEvent(Ljava/

[Efstathios Kalyvas]

I have the same issue. I have stopped using dev mode and i reverted to standard mode.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

[Jim Douglas]

...or temporarily switch to the stable channel.

> > google-web-tool...@googlegroups.com<google-web-toolkit%2Bunsubs cr...@googlegroups.com>
> > .

[Thomas Broyer]

Or temporarily switch to Firefox 3.x ;-)

[al...@mechnicality.com]

Sadly, that doesn't work for me because I am developing a WebGL based app and that only works with
Chrome or FF 4.

I've reverted to an earlier nightly build until the issue is fixed.

And, of course, I'm wondering when FF4 will be supported in GWT - but that's another story (and
thread) entirely. In August I heard it was "real soon now"...

Alan

On 12/20/2010 8:26 AM, Thomas Broyer wrote:
> Or temporarily switch to Firefox 3.x ;-) --

> You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
> To post to this group, send email to google-we...@googlegroups.com.

> To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.

[John A. Tamplin]

On Monday, December 20, 2010 11:44:11 AM UTC-5, alanmechy wrote:

And, of course, I'm wondering when FF4 will be supported in GWT - but that's another story (and
thread) entirely. In August I heard it was "real soon now"...

The problem was that every new beta of FF4 broke the APIs we were using, so we stopped trying to follow them until they settled down.  Supposedly the APIs are final as of 4.0b7, so Chris Conroy is working on it now.

[al...@mechnicality.com]

Hi John

Thanks for that update - looking forward to seeing it all work. I also appreciate that its not an easy task!

Regards

Alan

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

-- 
Alan Chaney
CTO and Founder, Mechnicality, Inc.
www.mechnicality.com

[funkforce]

Same problem here. Is there a way to go back to old Chrome? Doesnt get
it to work in FF 4 beta also.

On Dec 20, 5:44 pm, "a...@mechnicality.com" <a...@mechnicality.com>
wrote:

[al...@mechnicality.com]

Go to http://build.chromium.org/f/chromium/snapshots/chromium-rel-xp/ and find a snapshot that works
for you.

I'm currently using 66202, dated Nov 15 2010

Open the folder labeled 66202, download the zip file, extract it and then navigate to Chrome.exe and
use it.
Experience indicates that its best:

1. To *NOT* have any other copies of Chrome/Chromium open before you open this one.
2. Stop any dev mode projects you have (that is, stop them running), close any current versions of
Chrome/Chromium, open the nightly as above and then start dev mode again. I don't believe that you
need to restart eclipse.

I'm using 66202, but you may find a later one works for you - remember that these are nightly builds
and may not work at all!

Hopefully the issue will be resolve shortly....

HTH

Alan

[Chris Conroy]

Chrome checks the profile directory to figure out if it needs to start a new session or attach to an existing one. You should be fine having an instance of Chrome open with an instance of Chromium since they use different profiles. If you want to have multiple instances of Chrome or Chromium, then simply launch your alternate with --user-data-dir=/path/to/alternate/profile/directory

[al...@mechnicality.com]

Thanks Chris

On 12/20/2010 2:46 PM, Chris Conroy wrote:

Chrome checks the profile directory to figure out if it needs to start a new session or attach to an existing one. You should be fine having an instance of Chrome open with an instance of Chromium since they use different profiles. If you want to have multiple instances of Chrome or Chromium, then simply launch your alternate with --user-data-dir=/path/to/alternate/profile/directory

OK - that makes sense. I made the comment below because I spent about an hour this morning experimenting with older nightly builds to try and find one that still worked (and didn't have any other problems.) I found that unless I was careful to make sure that I'd closed the previous nightly build I was getting conflicting results because double-clicking on XXX when I had YYY already open of course meant that I was still using YYY. In other words, I wasn't trying to have *multiple* entries open, I was just needed to make sure that the entry I had open was *different* from the previous try. As I said below 66202 seems to work. I tried 66482 for a while, but the debug console didn't seem to work properly on that. 66202 is 9.0.584.0 (66202). As a matter of interest,  I couldn't find *any* version with "10." in it which didn't show http://code.google.com/p/google-web-toolkit/issues/detail?id=5778 - but then, you probably already know that!


Regards

Alan