Gwtquery and Vaadin modul inherit order

[GoogleCodeExporter]

Inherit Gwtquery AFTER DefaultWidgetSet, so your widgetset xml should looks 
like this:

<module>
    <inherits name="com.vaadin.DefaultWidgetSet" />
    <inherits name="com.google.gwt.query.Query"/>
</module>

After you compile the widgetset, you will get blank page and see some errors in 
the generated *cache.html files.

I use gwtquery 1.3.3 and vaadin 7.0.4

If you change the inherit order of this two modules, the problem will be 
solved, but I wonder what else options I have to fix this.

Original issue reported on code.google.com by juge...@gmail.com on 8 May 2013 at 1:55

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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

[GoogleCodeExporter]

Original comment by julien.d...@gmail.com on 14 Jul 2013 at 11:27

• Changed state: Invalid