Re: CSS exception compiling 2.7.0 app

Make sure gwt-dev.jar is first in class path. Most likely some other libraries you are using are also using flute but with a different/older version than GWT. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group

Re: CSS exception compiling 2.7.0 app

Hello? Is anybody out there? I have several GWT apps, I am having this issue with all of them, it's very freaky. The problem stems from one particular css file, NativeHorizontalScrollbarTransparent.css, which has a defined attribute who's name includes a "_". I'm not a CSS guy, but this seems

Re: [gwt-contrib] Re: GWT 2.8.0 RC2 is here!

We are doing a last minute fix. Next RC should be ready very soon and if no major issues it will be called final release around 2-3 weeks. On Wed, Sep 28, 2016 at 3:16 AM, Hitesh Kumar wrote: > Is there an ETA on GWT 2.8.0 release? > > On Friday, 12 August 2016 06:49:03

Re: GWT Maven project made with WebAppCreator don't work in devmode

I answered on SO: https://stackoverflow.com/a/39750766/116472 On Wednesday, September 28, 2016 at 3:51:20 PM UTC+2, Vit Vyaz wrote: > > Hi, all > > > I have created a GWT project with maven configuration on this way: > > webAppCreator -out HelloWorldGWT -templates sample,maven,readme >

GWT Maven project made with WebAppCreator don't work in devmode

Hi, all I have created a GWT project with maven configuration on this way: webAppCreator -out HelloWorldGWT -templates sample,maven,readme ua.vitvyaz.hellowordgwt.HelloWorldGWT I tried to run project on devmode: mvn gwt:devmode But in the browser I got: "HTTP ERROR 404 Problem

Re: Window.open does nothing in windows mobile 10 (IEEdge)

Does anyone know if this has been fixed? http://blog.daniel-kurka.de/2012/05/mobile-webkit-alert-dialog-breaks-touch.html My problem is with MGWT. It fixes the above bug by using a deferred ScheduledCommand to fire MGWT events e.g. a TapEvent.This is causing me the problem in IEEdge mobile

Re: [GWT 2.8 SHNAPSHOT] missing stack trace for 'Should only call onDetach when the widget is attached to the browser's document'

Thomas, Yes, that is what I ended up doing at the end After some more digging though, I realised there maybe a reason why the stack trace comes like that: https://github.com/Putnami/putnami-gradle-plugin/issues/49 -- You received this message because you are subscribed to the Google

Re: [GWT 2.8 SHNAPSHOT] missing stack trace for 'Should only call onDetach when the widget is attached to the browser's document'

How about setting a breakpoint at the throw line in Widget onDetach then? -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to