Hi Rasmus,
on the GWT.create I had a short discussion with Brain Slesinsky, he seems
to be responsible for the Super Dev Mode.
He told me that he has a tool to validate the generated Source Map, but he
was nut sure if he could made this tool open source :)
Do you have only the problem when you
We are fighting with this issue as well.
Any progress/Fix/Workaround found?
On Wednesday, 21 January 2015 20:24:00 UTC+1, Rocco De Angelis wrote:
> Somebody fighting with the some issue?
>
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" grou
Short update:
Okay it seems that the problem is somewhere in the generated source maps.
Some of our GWT modules work completely fine with Super Dev Mode withe the
current GWT version 2.7 (trunk) and Chrome 40.
But when I try to debug one of our largest modules I'm not able to
correctly debut the
Hi Jens,
yes sane behavior in Chrome stable. The gray and white lines seems to be
correct. But when I run into a break point the local variables a completely
incorrect and when I try to step over the code I get really strange jumps. The
same behavior appears also in IE11. But it's strange that
I would first blame Chrome if you use the dev channel of Chrome. Try beta
or stable channel and see if you still have issues. Also note that you can
not set break points in grey lines since they do not have source mapping
information.
-- J.
--
You received this message because you are subscri
Hi all,
I'm very happy with the super dev mode. Recompiling after a change takes
between 2-3 secs.
But with the current state of GWT 2.7 (trunk) I'm not able to make some
break points in Chrome (41 dev) or IE11?
It seems that the generated source maps are not correctly because some
break point
