Closed GoogleCodeExporter closed 9 years ago
Apart from the blank page, do you get any error in devmode?
Original comment by man...@talkwheel.com
on 9 May 2013 at 5:44
I've noticed if I put this line after inheriting modules:
<add-linker name="xsiframe"/>
it works fine.
In Query.gwt.xml[137] there is another linker definition that causes the
problem:
<!-- IE8 needs the iframe where the js of app is loaded set to standard in order
to use the queryAll native selector -->
<define-linker name="stddoctype"
class="com.google.gwt.query.linker.IFrameWithDocTypeLinker"/>
<add-linker name="stddoctype"/>
In Vaadin.gwt.xml there is xsiframe.
Original comment by juge...@gmail.com
on 9 May 2013 at 9:08
It seems that vaadin does not work with the standard linker.
In gwt you can only have a primary linker. By default in Core.gwt.xml the
standard linker is selected.
<add-linker name="std" />
What does gwtquery is to modify the std linker so as if a project is not
selecting any linker, the default std linker will work better with IE8.
But vaadin is seting xsiframe, proly because they dont support the std one, so
in this case it is mandatory that you put vaadin at the end.
Gwtquery works with any linker, even with std because ie8 selector will
fallback.
I dont think there is so much we can do, apart from document this issue in the
Query.gwt.xml file
Original comment by manuel.carrasco.m
on 15 May 2013 at 2:39
I've migrated this issue to github :
https://github.com/gwtquery/gwtquery/issues/213
Please follow the issue there.
Original comment by julien.d...@gmail.com
on 14 Jul 2013 at 11:25
Original comment by julien.d...@gmail.com
on 14 Jul 2013 at 11:27
Original issue reported on code.google.com by
juge...@gmail.com
on 8 May 2013 at 1:55