Hello,
the advice to use an UncaughtExceptionHandler was very helpful for solving
this acutal problem.
But it also has a disadvantage: It brings to light new problems! :-)
But because it would be offtopic here I have started another thread:
CellTable - TextColumn.getValue (null) - another
but why was this exception not reported as others client-side exceptions
are?
In IE + DevMode you would have seen a NullPointerException on the console.
If you use Chrome/Firefox + DevMode you never see the problem because both
browser support the Audio element and thus its never null.
The exception occurrs somewhere in a constructor where a panel is created.
At the moment it would be of help, if I could see how the source is
translated into JS. But IE shows only the code from the host page. No idea
how to update it.
Compile your app in PRETTY or DETAILED mode so that
Hi,
setting the compiler mode to pretty did not result in a more
comprehensive error message:
com.google.gwt.core.client.JavaScriptException: (TypeError)
description: 'null.nullField' ist Null oder kein Objekt
But I finally found the nullpointer exception by tracing. It happened in
the newly
Audio element is supported from IE 8 according to
thishttp://caniuse.com/#search=audio
.
Always use the static method isSupported() for all
@PartialSupporthttp://www.gwtproject.org/javadoc/latest/com/google/gwt/dom/client/class-use/PartialSupport.htmlclasses
for runtime check.
On Monday, June
Ok,
but why was this exception not reported as others client-side exceptions
are?
For example, if you add a widget to a DockLayoutPanel after the center
widget, you get a comprehensive error message.
In this case with the audio, I never have seen any comprehensive message,
even after setting
Hi Jens!
1.) use SafeHtmlUtils instead
of OnlyToBeUsedInGeneratedCodeStringBlessedAsSafeHtml.
Ok!
2.) always use !DOCTYPE html in your host html page so that IE is in
standards mode to avoid head aches :)
This is already the case. In addition, I jhave already tried different
Hello,
I have a very strange problem with some anchors, which occurrs only in IE
and only in certain combinations of version and browser/document modes.
The problem is, that *some* anchors will not work, allthough *all* anchors
are built by the same method!
There is a list of chess games and
Hi Magnus,
Just for the sake of thoroughness, are you sure that onCommand is even
being called? Or is it that the click event is not being registered at all?
On Friday, June 21, 2013 11:33:47 AM UTC+2, Magnus wrote:
Hello,
I have a very strange problem with some anchors, which occurrs only
Am Freitag, 21. Juni 2013 12:48:51 UTC+2 schrieb GWTter:
Just for the sake of thoroughness, are you sure that onCommand is even
being called? Or is it that the click event is not being registered at all?
Yes! Because it works with other browsers.
In addition, the second link (Analyze) also
Hi,
my problem is that I cannot analyze what happens.
In chrome (where it works), I can examine the code and it looks like the
code below. The two links are exactly the same, with a space between them
realized as nbsp;.
But maybe in IE the code looks different. The same for the JS code. IE
IE has had developer tools built in as far back as version 8, just press
F12. If you're working with =IE7 then: IE dev
toolshttp://www.microsoft.com/en-us/download/details.aspx?id=18359.
Although it may work in other browsers or on the other anchor you want to
see exactly what is or isn't
I've found that with the IE developer tools, you need to refresh the DOM
view within the tools (there's a refresh icon in the HTML view section).
The view doesn't seem to take the JS changes to the page into account
initially. (And sometimes you never see CSS that GWT injects, but that's
Hello,
I found another hint, that may be useful: Within the same application I do
the same thin in a toally other way: This time, the list is a CellTable and
the commands are rendered as a custom cell (see below). The anchors are
created in a totally different way. But the same problem exists
General advice:
1.) use SafeHtmlUtils instead
of OnlyToBeUsedInGeneratedCodeStringBlessedAsSafeHtml.
2.) always use !DOCTYPE html in your host html page so that IE is in
standards mode to avoid head aches :) Also, if possible in your setup, let
the webserver/appserver detect if IE is running
15 matches
Mail list logo
