> 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 [email protected]. 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.
