Google Web Toolkit

Friday, May 2, 2014

nocache.js Throws SecurityError When Local Data is Disabled (Storage Detection is Broken)

When Chrome (34.0.1847.131) is configured to "Block sites from setting any data", it throws a SecurityError whenever localStorage or sessionStorage is accessed. As a result, apps with dev redirect enabled fail to load.

Try it yourself. Settings > Show advanced settings... > Privacy > Content settings... > Block sites from setting any data. Then open the inspector and load http://www.gwtproject.org/.

Based on the comments it looks like storage detection was tested with this setting, so did Chrome's behavior change? I haven't tried it with other browsers...

Thanks,

David

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Printing with RootPanel vs RootLayoutPanel

I found a workaround in the end, I had a pretty much emprty body tag in my app html page, I foun dif I filled it with a load of <br/> 's it printed out fine in chrome

On Friday, 30 March 2012 00:40:57 UTC+1, Ted wrote:

Hello,

I have a GWT "page" created with UiBinder that I want to print. The top level element is a g:ScrollPanel with g:VerticalPanel. When I add the view to RootPanel I can print it just fine. When I add to RootLayoutPanel and try to print, I only get a blank page.

Does anyone know why this might be the case?

Thanks.

Ted

How to disable specific pruning/inlining with GWT compiler?

I have been trying to create an API, such that it would "look and feel" the same, both from GWT Java code, and from manually written JavaScript code. After much Googling, I came to gwt-exporter, which is the "universal answer" used, for anyone trying to do such a thing. So I gave it a try; unfortunately, things did not go well, as explained in this post to the gwt-exporter forum: Is there an ETA for GWT 2.6 support?

Having received no answer in 3 days, I have decided to try and do it "manually". I haven't had any success here either, but I think I have found the true problem: GWT just kills (some of) my code, because it thinks it's "not being used" (or perhaps, "inline" some methods, causing then to not be available anymore). In any case, the methods are *gone*. Looking for a solution to *that problem*, I get back to posts saying to use gwt-exporter there too. So I'm stuck in an infinite loop with no way out.

One critical difference to the "usual case", is that the manually written JavaScript code does not come from a JSNI call, but from an "external source", and so is *not available at compile time*. A compiler flag telling the compiler not to "prune" something would not be useful in this case; the flag/marker needs to be specific to classes and methods, instead of applying globally.

As I did not get any answer on the gwt-exporter forum in 3 days, and have therefore no way of knowing if, and when, gwt-exporter will be updated, I was hoping someone could point me to a solution that would provide the following benefits, even if it involves much boiler-plate GWT/JSNI code:

1) Instances of "marked" types can be created from JavaScript (in or out of JSNI, like from dynamically generated scripts, or scripts typed directly in the app UI), using the fully-qualified, non-obfuscated, Java class name. This should still work, if no code refers to that class, either from Java or JSNI.

2) All the public (at least) methods on the types selected in 1) will be available in JavaScript, using their simple, non-obfuscated, name (this probably preclude method overloading). It should work for both instance, and static methods. This should still work, if no code refers to that method, either from Java or JSNI.

3) (Optional) Same as methods, but for fields too.

The "end goal" is to allow users some limited ability to "customize" the application by "injecting user scripts" into it.

I would be grateful for any help.

Regards,
Sebastien Diot

Re: Printing with RootPanel vs RootLayoutPanel

Hi,

Did you ever find out what was going on here? I have the same problem, but only in chrome (Version 36.0.1964.4 dev-m), in all other browsers I've tested it prints out fine!

Thanks

On Friday, 30 March 2012 00:40:57 UTC+1, Ted wrote:

Hello,

I have a GWT "page" created with UiBinder that I want to print. The top level element is a g:ScrollPanel with g:VerticalPanel. When I add the view to RootPanel I can print it just fine. When I add to RootLayoutPanel and try to print, I only get a blank page.

Does anyone know why this might be the case?

Thanks.

Ted

Re: Printing with RootPanel vs RootLayoutPanel

Hi,

Did you ever find out what was going on here? I have the same problem

Thanks

On Friday, 30 March 2012 00:40:57 UTC+1, Ted wrote:

Hello,

I have a GWT "page" created with UiBinder that I want to print. The top level element is a g:ScrollPanel with g:VerticalPanel. When I add the view to RootPanel I can print it just fine. When I add to RootLayoutPanel and try to print, I only get a blank page.

Does anyone know why this might be the case?

Thanks.

Ted

Thursday, May 1, 2014

Re: SDM/UIBinder phantom compile error won't go away, can't build app

Could be the unit-cache. Defaults to a ".gwt-unitCache" directory sibling to your "war" directory.

On Wednesday, April 30, 2014 11:27:34 PM UTC+2, Michael Brown wrote:

Color me stoopid but...

I've got a phantom compile error that shows up building with SDM (and prevents me from launching SDM) but not otherwise. No complaints from Eclipse 4.3. Cleaning Eclipse project and relaunching Eclipse doesn't help, nor does restarting Firefox ESR 24.4 or even rebooting my Centor 5.1 dev box. I'm attempting to develop/build an MVP app GWT 2.6 and UIBinder..

I'm getting a complaint out of UIBinder trying to build one of my views. View used to extend DockLayoutPanel (constructor requires Style.Unit arg) but now extends SimpleLayoutPanel (I'm now putting the DockLayoutPanel within the SimpleLayoutPanel). UIBinder complains about my view not having a constructor with the Style.Unit arg. It's right that there is no such constructor, but wrong to think it needs one. I've thoroughly searched all the code and don't see any reason SDM/UIBinder should think I'm still using DockLayoutPanel instead of SimpleLayoutPanel as the root for this view.

I recall reading a post a while back (can't find it now) that indicated sometimes these phantom compile error stick around and won't go away until you delete some (error log?) file. Anyone know what file that would be? Is finding/deleting this file a viable solution or should I do something else instead?

I'd really like to use UIBinder but I've been stumped on this issue for a couple of days now and am about ready to rip out the UIBinder stuff and go back to building the UI by hand. Bummer!

Thanks for any clues....

Mike

Re: Why won't the GWT 2.1 MVP example compile?

This is as crazy as it could be. Why can't they add it in documentation!