setVisible issues with Firefox, then display: none !important

2012-06-12 Thread Domenec
Hello, about to deploy to production an evolution of a project, customer calls and says hidding icons fails in Firefox. What? Firebug to the rescue says the icons have a nice display: none after I call setVisible(false). Changing by hand to display: none !important works and I accept it as a

Bug? this$static.element is null exception in com.google.gwt.user.client.ui.Image constructor

2009-07-30 Thread Domenec
This is happening on GWT 1.7 sometimes and randomly on an Ubuntu box using FF3.0 The exception first happened in an imatge.setWidth (that was GWT 1.5.3), so I added a getElement check (and reordered the code) Now it is happening in the constructor, which is weird and out of control... ** This

module.nocache.js getting cached

2009-07-30 Thread Domenec
For several reasons I was thinking that it did happen, although [1] explains that it shouldn't happen. [2] shows a couple of methods to prevent that this file gets cached. In my case, server side exceptions [3] were being thrown for RPC calls from Ubuntu+FF3.5, saying that serialization

Most polite way to wait for applet load in onModuleLoad in Safari?

2009-07-17 Thread Domenec
Hello and thanks in advance... This is a Safari issue, this browser seems not wait to for onLoad JavaScript event. My onModuleLoad communicates with a Java applet and what works on FF+IE (they wait for the applet to load, then trigger onLoad) does not work for Safari, which triggers onLoad

Two pieces of Safari weirdness, and how to fix them

2009-07-17 Thread Domenec
Weirdness one. GWT code calls JSNI method which calls Java applet to retrieve a String. Back in GWT, a .indexOf or .length or any function on the variable which stores the applet String fails. Window.alert (length=+variable.length()) shows function length() { [native code] }, which is really

Sharing GWT classes between two projects with a Maven build

2009-03-19 Thread Domenec
Hello, my setup is: Application #1 is a GWT app. There is RPC, so the interfaces and associated POJO's that define the RPC call are within the client package, so that they can be translated into JavaScript. On the server side of app#1 there is a call to web services. Those web services are