So I looked at the logging module's xml files and it seems most of the things I'm disabling are disabled by default. So, I changed my module file to just be this:
And I'm still getting the white popup. Looking at the GWT source code it appears it is coming from LoggingPopup but this is only called by PopupLogHandler. This should be disabled by the log module here (in LoggingDisabled.gwt.xml which is inherited by Logging.gwt.xml):
But it doesn't seem to be working. So what am I doing wrong? I can't be the only one compiling on linux with logging and seeing this, right?
On Monday, January 26, 2015 at 5:47:07 PM UTC-8, rjcarr wrote:I'm using client logging and have been for a while. Things worked fine in 2.6 but when I switched to 2.7 I got a few logging config errors as handlers were no longer supported. After correcting these and opening my app in a browser I get a white popup window in the upper left (looks like this http://imgur.com/Xavu6K7)
. Strangely, this only shows up when building and running on linux; when running on a mac the popup never appears.The relevant parts of module file looks like this:
Basically, all I want is the console handler as I'm doing everything else with a custom handler (it's silly these aren't disabled by default). My custom handler extends Handler and is pretty simple. It is created like this:
And I'm sure the white popup isn't coming from there. So what's going on? And isn't this some sort of GWT defect if things behave differently on different platforms using identical codebases?
Thanks for the help!
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To post to this group, send email to email@example.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.