It definitely appears to be the case that having multiple GWT window
objects (as frames) is playing a role in the problem. The main window has
two frames, and some GWT JSNI runs inside each of the two frames. When
JSNI in one frame calls the other, the type information on the passed
objects e
We have a huge Framework so that may not be an easy task - but I'll see if
I can get a standalone case.
Within the stack frame I was investigating, I noticed that the window
object seemed to change across frames, so perhaps the $entry() arguments
were stripped of some of their properties (or th
Could you post a snippet reproducing the issue?
--
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this gro
This is not wrong, but not a real vulnerability either I believe, if only
because, to begin with, downloads are made through HTTPS.
(Don't take my words for granted though, I'm not a security expert)
Wrt your first question, have a look at
http://www.gwtproject.org/makinggwtbetter.html
You could
We're seeing an issue in GWT 2.7.0 where if a Java Object is passed to a JS
method that's wrapped with $entry(), then the type information is stripped
off.
So for example, if a LinkedMap instance is created, and passed through an
API wrapped with $entry(), it's typeMarker$ attribute will be c
