executeJavaScript and window initialization order problem

[joonaslehtinen]

@T de Koning

setTimeout() would not be a good solution for this problem, because you never know when the page is actually finished.

Vaadin TestBench product has implemented this in roughly the following manner. You might use this to wait for vaadin to finish rendering before printing, but I have not tested it:

if (wnd.wrappedJSObject) {
		wnd = wnd.wrappedJSObject;
}

var connector = null;
if (wnd.itmill) {
	connector = wnd.itmill;
} else if (wnd.vaadin) {
	connector = wnd.vaadin;
}

var clients = connector.clients;
if (clients) {
			  for ( var client in clients) {
				  if (clients[client]
.isActive()) {
					  return false;
				  }
			  }
			  return true;
		  	} else {
		  		//A Vaadin connector was found so this is most likely a Vaadin application. Keep waiting.
		  		return false;
		  	}
	 }, timeout);

@T de Koning

Is there a way to use the vaadin components and generate plain html or pdf (or similar) so it can be printed?
It is not desired to build an entire html report just for printing this page (the lay-out is quite complicated and will change in the future).

There is no separate rendering pipeline for static HTML or PDF. So your options are to either to 1) create the static html or pdf for printing with some other tool, 2) use long enough setTimeout or 3) get the above wait for vaadin javascript approach to work.