[gwt-contrib] Re: CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

[Brandon Donnelson]

I haven't dug in yet, just wanting to use it. That sounds promising. Using 
bookmarlets doesn't work when the module is embedded in another iframe. so 
the next issue I need to deal with is helping detect the module when it's 
not in the main body but in another iframe of the document. 

The other workaround is to implant the project.nocache.js js launching in 
the war and send it off to the external server. So this makes another 
problem I have hit a couple times. Where I change the var hostName = 
"127.0.0.1";  to a specific ip because I loaded the app with 
project.nocache.js. I like this hack but I'm wishing I could set that in 
the code server launcher arguments. 

Anyway it's all about using an external server. 

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/41735d5b-1848-44e6-be31-3a34d87ddec7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Last call for 2.8.0-RC3

[Thomas Broyer]

As we've delayed the release a bit, let's add another documentation fix: 
https://gwt-review.googlesource.com/16860

On Thursday, September 8, 2016 at 4:27:36 PM UTC+2, Daniel Kurka wrote:
>
> Hi all,
>
> I will be cutting rc3 tomorrow 1pm CEST, please respond to this email with 
> any outstanding reviews that you want to see included.
>
> -Daniel
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/7d8ef60a-3485-4b33-befe-8d1c15676cd4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: ScriptInjector seems to be broken (2.8-SNAPSHOT)

['Goktug Gokdogan' via GWT Contributors]

We should hold up the release. There is another path around arrays as well.

On Fri, Sep 9, 2016 at 8:04 AM, Colin Alworth  wrote:

> Another issue at may warrant attention - https://github.com/
> gwtproject/gwt/issues/9424. This was brought up some time ago, but wasn't
> reduced to be reproducible until now (which is funny, given how minimal the
> test case is).
>
> On Fri, Sep 9, 2016 at 9:30 AM 'Daniel Kurka' via GWT Contributors <
> google-web-toolkit-contributors@googlegroups.com> wrote:
>
>> +Goktug Gokdogan  +Roberto Lublinerman
>>   Should we be holding RC3, I guess so right?
>>
>> On Fri, Sep 9, 2016 at 4:12 PM Jens  wrote:
>>
>>>
>>> Can you file an issue and ping Daniel (by mail or hangout) to delay the
 RC3 a bit? (if not already too late, as it's 4pm cest)

>>>
>>> Done.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "GWT Contributors" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> .
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/google-web-toolkit-contributors/6386bb88-f488-
>>> 4144-b830-99ddb387b677%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "GWT Contributors" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/google-web-toolkit-contributors/CALLujirOwMPQTKzDuJtmtF0hF2bXV
>> r%3Dij-V240vzP6Bh5SMRAA%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA3e16Cw5iFU9qDNAP7XYwnpZm571vhJtDSYycDGzdTEtA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Last call for 2.8.0-RC3

['Roberto Lublinerman' via GWT Contributors]

Arnaud, have you tried using -strict? GWT ignores compilation units with
errors if they are not explicitly reachable from the entry point. I assume
your Toto class is only referenced from JS. So if this class has any
compile error (like missing references) then GWT does not see the class,
much less know it is a JsType. Strict mode should give you an error in this
case.

On Fri, Sep 9, 2016 at 6:09 AM, Arnaud TOURNIER  wrote:

> I have one problem which is recurring, related to JsInterop.
>
> Sometimes the JsInterop JS stub is not generated because of (seemingly) an
> internal error in SuperDevMode (and GWTC it seems), but nothing is logged,
> so it's difficult to diagnose.
>
> For example, in an application (which does not inherits the User module),
> when i write a class like this, the JS stub is generated correctly :
>
> @JsInterop
> public class Toto
> {
> public void doSomething()
> {
> // really nothing here...
> }
> }
>
> But if i change it to :
>
> @JsInterop
> public class Toto
> {
> public void doSomething()
> {
> Window.alert( "yeah" );
> }
> }
>
> Then the JS stub is not generated (i mean the Toto constructor function is
> not made available to JS scope).
>
> I understand that Window.alert(...) is implemented in the User module and
> since i don't inherit from it, the thing cannot be generated. But no
> message is generated (neither by SDM nor by the GWTC if i remember well),
> which is then difficult to diagnose...
>
> Note : i should be able to produce a minimal repro case for this thing.
>
>
> Then sometimes, a @JsInterop class would not be exported to JS, but if i
> change its name then it's generated, which is... weird.
>
> For this one i am not sure i can give a minimal repro case because it
> happens on quite large projects (angular2 with gwt 2.8)...
>
>
> I saw another error:
>
> It was in a @JsInterop class, which called a template method (i mean with
>  in the signature of the method). I had to specify the  type to call
> it to have the SDM generating the class. If i didn't, the javac would infer
> correctly the  type (so no error appears in the IDE, which is Eclipse in
> my case), but it seemed that SDM did not manage to infer the type correctly
> because then the class would not be accessible from javascript... I can
> give you a sample file if you need.
>
>
> A last one : i tried migrating a big app from 2.7 to 2.8-rc2 (same problem
> with previous sub versions of the 2.8). The compiler goes on compiling then
> does the linking, but it suddenly crashes without saying anything (i tried
> TRACE and DEBUG log levels with no more useful information) and results in
> a maven build failure. The build is happening in maven. Since the app is
> quite big, i guess the problem comes from a dependency i use which is not
> 2.8 friendly (did not have enough time to investigate that deeply). But
> again, the problem is not that the compile does not work, but that no
> useful message is generated to understand the error.
>
> For this one, i can give you the code, but privately since it is a
> business app that is not open source...
>
> Thanks !
>
> Arnaud Tournier
> LTE Consulting
>
>
> Le jeudi 8 septembre 2016 16:27:36 UTC+2, Daniel Kurka a écrit :
>>
>> Hi all,
>>
>> I will be cutting rc3 tomorrow 1pm CEST, please respond to this email
>> with any outstanding reviews that you want to see included.
>>
>> -Daniel
>>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/5e5b6585-aba1-
> 48ce-a5d6-6f9a702e801b%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7g%3DOvF6Bu%2BmFdYDmNF2F11zQgDxdFo65j6zTYnWFQr2ZXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: ScriptInjector seems to be broken (2.8-SNAPSHOT)

[Colin Alworth]

Another issue at may warrant attention -
https://github.com/gwtproject/gwt/issues/9424. This was brought up some
time ago, but wasn't reduced to be reproducible until now (which is funny,
given how minimal the test case is).

On Fri, Sep 9, 2016 at 9:30 AM 'Daniel Kurka' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> +Goktug Gokdogan  +Roberto Lublinerman
>   Should we be holding RC3, I guess so right?
>
> On Fri, Sep 9, 2016 at 4:12 PM Jens  wrote:
>
>>
>> Can you file an issue and ping Daniel (by mail or hangout) to delay the
>>> RC3 a bit? (if not already too late, as it's 4pm cest)
>>>
>>
>> Done.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "GWT Contributors" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/6386bb88-f488-4144-b830-99ddb387b677%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirOwMPQTKzDuJtmtF0hF2bXVr%3Dij-V240vzP6Bh5SMRAA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CADcXZMz0S2wLjhN%2BKuTs4F84kUfnNHtqkDiKeJtjbqUf_piOhg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: ScriptInjector seems to be broken (2.8-SNAPSHOT)

['Daniel Kurka' via GWT Contributors]

+Goktug Gokdogan  +Roberto Lublinerman
  Should we be holding RC3, I guess so right?

On Fri, Sep 9, 2016 at 4:12 PM Jens  wrote:

>
> Can you file an issue and ping Daniel (by mail or hangout) to delay the
> RC3 a bit? (if not already too late, as it's 4pm cest)
>
>
> Done.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/6386bb88-f488-4144-b830-99ddb387b677%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujirOwMPQTKzDuJtmtF0hF2bXVr%3Dij-V240vzP6Bh5SMRAA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: ScriptInjector seems to be broken (2.8-SNAPSHOT)

[Jens]

> Can you file an issue and ping Daniel (by mail or hangout) to delay the 
> RC3 a bit? (if not already too late, as it's 4pm cest)
>

Done.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/6386bb88-f488-4144-b830-99ddb387b677%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: ScriptInjector seems to be broken (2.8-SNAPSHOT)

[Thomas Broyer]

Can you file an issue and ping Daniel (by mail or hangout) to delay the RC3 
a bit? (if not already too late, as it's 4pm cest)

On Friday, September 9, 2016 at 3:51:05 PM UTC+2, Jens wrote:
>
> Ok just tried it myself.
>
> Created a new, fresh project having world in my 
> host page using
>
> public void onModuleLoad() {
>   Global.window.alert("Element found: " + (Global.document.getElementById(
> "hello") != null));
> }
>
>
> GWT 2.8 RC2 returns true
>
> _.onModuleLoad_4_g$ = function onModuleLoad_3_g$(){
>   ($clinit_Global_0_g$() , $wnd.window.window).alert('Element found: ' + 
> jsNotEquals_0_g$(($clinit_Global_0_g$() , $wnd.window.document).
> getElementById('hello'), null));
> }
>
>
>
> GWT 2.8 SNAPSHOT (09.09.2016) returns false
>
> _.onModuleLoad_4_g$ = function onModuleLoad_3_g$(){
>   ($clinit_Global_0_g$() , window).alert('Element found: ' + 
> jsNotEquals_0_g$(($clinit_Global_0_g$() , document).getElementById('hello'
> ), null));
> }
>
>
>
> So I guess its a bug in GWT 2.8 SNAPSHOT as I think the JS output of GWT 
> 2.8 SNAPSHOT should be that way it is above if @JsType(isNative = true, 
> namespace = "window") is used. However elemental2 uses JsPackage.GLOBAL 
> as namespace.
>
>
> -- J.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/48cd290e-c2c0-45a3-b555-29936103c8cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: ScriptInjector seems to be broken (2.8-SNAPSHOT)

[Jens]

Ok just tried it myself.

Created a new, fresh project having world in my host 
page using

public void onModuleLoad() {
  Global.window.alert("Element found: " + (Global.document.getElementById(
"hello") != null));
}


GWT 2.8 RC2 returns true

_.onModuleLoad_4_g$ = function onModuleLoad_3_g$(){
  ($clinit_Global_0_g$() , $wnd.window.window).alert('Element found: ' + 
jsNotEquals_0_g$(($clinit_Global_0_g$() , $wnd.window.document).
getElementById('hello'), null));
}



GWT 2.8 SNAPSHOT (09.09.2016) returns false

_.onModuleLoad_4_g$ = function onModuleLoad_3_g$(){
  ($clinit_Global_0_g$() , window).alert('Element found: ' + 
jsNotEquals_0_g$(($clinit_Global_0_g$() , document).getElementById('hello'), 
null));
}



So I guess its a bug in GWT 2.8 SNAPSHOT as I think the JS output of GWT 
2.8 SNAPSHOT should be that way it is above if @JsType(isNative = true, 
namespace = "window") is used. However elemental2 uses JsPackage.GLOBAL as 
namespace.


-- J.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/25c12ba5-120c-47e0-b52a-c386691b9618%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: Last call for 2.8.0-RC3

[Arnaud TOURNIER]

I have one problem which is recurring, related to JsInterop.

Sometimes the JsInterop JS stub is not generated because of (seemingly) an 
internal error in SuperDevMode (and GWTC it seems), but nothing is logged, 
so it's difficult to diagnose.

For example, in an application (which does not inherits the User module), 
when i write a class like this, the JS stub is generated correctly :

@JsInterop
public class Toto
{
public void doSomething()
{
// really nothing here...
}
}

But if i change it to :

@JsInterop
public class Toto
{
public void doSomething()
{
Window.alert( "yeah" );
}
}

Then the JS stub is not generated (i mean the Toto constructor function is 
not made available to JS scope).

I understand that Window.alert(...) is implemented in the User module and 
since i don't inherit from it, the thing cannot be generated. But no 
message is generated (neither by SDM nor by the GWTC if i remember well), 
which is then difficult to diagnose...

Note : i should be able to produce a minimal repro case for this thing.


Then sometimes, a @JsInterop class would not be exported to JS, but if i 
change its name then it's generated, which is... weird.

For this one i am not sure i can give a minimal repro case because it 
happens on quite large projects (angular2 with gwt 2.8)...


I saw another error:

It was in a @JsInterop class, which called a template method (i mean with 
 in the signature of the method). I had to specify the  type to call 
it to have the SDM generating the class. If i didn't, the javac would infer 
correctly the  type (so no error appears in the IDE, which is Eclipse in 
my case), but it seemed that SDM did not manage to infer the type correctly 
because then the class would not be accessible from javascript... I can 
give you a sample file if you need.


A last one : i tried migrating a big app from 2.7 to 2.8-rc2 (same problem 
with previous sub versions of the 2.8). The compiler goes on compiling then 
does the linking, but it suddenly crashes without saying anything (i tried 
TRACE and DEBUG log levels with no more useful information) and results in 
a maven build failure. The build is happening in maven. Since the app is 
quite big, i guess the problem comes from a dependency i use which is not 
2.8 friendly (did not have enough time to investigate that deeply). But 
again, the problem is not that the compile does not work, but that no 
useful message is generated to understand the error.

For this one, i can give you the code, but privately since it is a business 
app that is not open source...

Thanks !

Arnaud Tournier
LTE Consulting


Le jeudi 8 septembre 2016 16:27:36 UTC+2, Daniel Kurka a écrit :
>
> Hi all,
>
> I will be cutting rc3 tomorrow 1pm CEST, please respond to this email with 
> any outstanding reviews that you want to see included.
>
> -Daniel
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/5e5b6585-aba1-48ce-a5d6-6f9a702e801b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: ScriptInjector seems to be broken (2.8-SNAPSHOT)

[David]

I'm sure my stuff was working fine with JsInterop 1.0 but with JsInterop
2.0 the only solution seems to be to use Global.top.window.document
As far as I remember I had it working somewhere half of July - but I might
be wrong. Can I force in maven to take a very specific snapshot version of
GWT 2.8.0, then I could double check ?

>From what you explain it seems like Global.window should have worked. But I
have this in my html:

I'm here!

Then when I try these:
Global.document.getElementById("test") -> null
Global.window.document.getElementById("test") -> null
Global.top.document.getElementById("test") -> [object HtmlDivElement]

Is this really how it should be ? I cannot use top since my app could be
embedded in an IFrame. I would have expected Global.document.getElementId
to have worked but it does not.

Anyway, maybe its because there is not enough docs available yet that I am
confused. Maybe it was accidentally working before and all this is just how
it is supposed to be ?


On Fri, Sep 9, 2016 at 12:13 PM Jens  wrote:

>
> This scoping is all very confusing :-).
>>
>> Anyway, this is what I am seeing with Elemental2:
>> - I have an application that generates HTML using a custom templating
>> system.
>> - I then put the HTML string in an Element with setInnerSafeHtml.
>> - After this I use Element2 to bind to the generated html. For that I was
>> using Global.document.getElementById(...).
>>
>> This used to work, but since a few weeks this stopped working.
>>
>> I now have to use Global.window.top.document.getElementById(...) to get
>> access to the ui dom nodes that I generated.
>>
>> Is this how it is supposed to be ? I was probably making the wrong
>> assumptions before ?
>>
>
> No. Elemental2's Global class uses @JsType(isNative = true, name =
> "window", namespace = JsPackage.GLOBAL) which translates to $wnd.window
> because JsInterop qualifies everything with $wnd (unless
> namespace="window" has been set as of the commit you have referenced
> before), JsPackage.GLOBAL is an empty namespace and window is the name.
>
> Are you sure nothing has changed in your app ?! I don't think something
> has changed in GWT as such (breaking) changes would normally cause more
> posts on gwt-contrib / gwt-user.
>
> -- J.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/9b7a6321-c9ca-44a8-bd8d-01e6dc113f13%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABrJHW2JDzPyAHXD6MVgazyPGb_5t8tugTJqKrR4vbzVN5XCOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: ScriptInjector seems to be broken (2.8-SNAPSHOT)

[Jens]

> This scoping is all very confusing :-).
>
> Anyway, this is what I am seeing with Elemental2:
> - I have an application that generates HTML using a custom templating 
> system.
> - I then put the HTML string in an Element with setInnerSafeHtml.
> - After this I use Element2 to bind to the generated html. For that I was 
> using Global.document.getElementById(...).
>
> This used to work, but since a few weeks this stopped working.
>
> I now have to use Global.window.top.document.getElementById(...) to get 
> access to the ui dom nodes that I generated.
>
> Is this how it is supposed to be ? I was probably making the wrong 
> assumptions before ?
>

No. Elemental2's Global class uses @JsType(isNative = true, name = 
"window", namespace = JsPackage.GLOBAL) which translates to $wnd.window 
because JsInterop qualifies everything with $wnd (unless namespace="window" 
has been set as of the commit you have referenced before), JsPackage.GLOBAL 
is an empty namespace and window is the name.

Are you sure nothing has changed in your app ?! I don't think something has 
changed in GWT as such (breaking) changes would normally cause more posts 
on gwt-contrib / gwt-user.

-- J.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/9b7a6321-c9ca-44a8-bd8d-01e6dc113f13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: ScriptInjector seems to be broken (2.8-SNAPSHOT)

[David]

This scoping is all very confusing :-).

Anyway, this is what I am seeing with Elemental2:
- I have an application that generates HTML using a custom templating
system.
- I then put the HTML string in an Element with setInnerSafeHtml.
- After this I use Element2 to bind to the generated html. For that I was
using Global.document.getElementById(...).

This used to work, but since a few weeks this stopped working.

I now have to use Global.window.top.document.getElementById(...) to get
access to the ui dom nodes that I generated.

Is this how it is supposed to be ? I was probably making the wrong
assumptions before ?



On Thu, Sep 8, 2016 at 11:17 PM 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> Global object is not scoped to window unless you explicitly say "window";
> so it should be $wnd by default.
>
> On Wed, Sep 7, 2016 at 2:50 AM, David  wrote:
>
>> I was depending on JsInterop Global.document to get access to UI
>> components generated by my template engine.
>> The Global object is now scoped window, so I guess it is accessing the
>> wrong document as well ?
>>
>>
>> On Wed, 7 Sep 2016 at 11:40, David  wrote:
>>
>>> I'm sure that it worked before. I'm also seeing some other issues where
>>> I am using JsInterop to interact with some generated HTML - but I am still
>>> investigating if that is due to changes in GWT or in our codebase.
>>>
>>> I did not work on this project for about 8 weeks, so I have quite a
>>> backlog to go through.
>>>
>>> On Tue, 6 Sep 2016 at 19:28, 'Goktug Gokdogan' via GWT Contributors <
>>> google-web-toolkit-contributors@googlegroups.com> wrote:
>>>
 It is surprising as Jens pointed out, we always qualified references
 with $wnd until https://gwt-review.googlesource.com/#/c/15520/
 (submitted 5 weeks ago). So it shouldn't have worked earlier if you were
 not injecting it to TOP_WINDOW.
 If it worked earlier, then we unintentionally fixed a bug. Could you
 double check if this was working before so we can see if there are some
 other unintended behavior change introduced somewhere else?

 On Tue, Sep 6, 2016 at 2:43 AM, stuckagain 
 wrote:

> It was working fine before.
>
> Since it looks like JsInterop has changed recently (and it is still in
> beta) I will just update my code to either inject in the TOP_WINDOW or I
> try it with using window as namespace.
>
>
> On Monday, September 5, 2016 at 6:29:48 PM UTC+2, Jens wrote:
>>
>> Hm wondering how it ever worked for you as JsInterop usually
>> qualifies JS code with $wnd but your D3.js has been injected into the GWT
>> iframe. So AFAICT with JsInterop you would had to use TOP_WINDOW anyways.
>> You can make it work within the GWT iframe but then you can't use
>> JsPackage.GLOBAL but use a namespace that points to the iframe content
>> window.
>>
>> Also see:
>> https://groups.google.com/d/msg/google-web-toolkit/GcsWUuzexvE/ApUg3sLZCQAJ
>>
>> So it looks like this behavior has changed? But yes you would need to
>> use "window" now to references the iframe's content window if you inject
>> the code into the iframe.
>>
>> -- J.
>>
> --
> You received this message because you are subscribed to the Google
> Groups "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
> google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/7862784c-854a-4bb1-85c0-2b7734a984d3%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

 --
 You received this message because you are subscribed to the Google
 Groups "GWT Contributors" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to
 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA0RioQk7GatwdbkvwZKT6gKDEmB0daytVoKa9a%3DnGUd3A%40mail.gmail.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>> --
>> You received this message because you are subscribed to the Google Groups
>> "GWT Contributors" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>>
> To view this discussion on

[gwt-contrib] Re: CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

[Thomas Broyer]

Doesn't CodeServer accept -setProperty? You could use that to pinpoint the 
property values so you only have one permutation when only user.agent is given.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/fe7f6b31-c172-4043-a56e-0b43d716c4a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.