You're right, I use Polymer.importHref() too, but I don't want to move this directly in the html as our project supports different UI toolkits, not only polymer, so it depends on the configuration and imports need to be done at runtime.
So I think I will open an issue and stay with beta1 until the issue is resolved. Thanks. On Friday, 12 August 2016 17:12:55 UTC+2, zakaria amine wrote: > > You must be using Polymer.importHref() right ? and then you call > Polymer.ready() I had the same issue before, and I ended up > removing Polymer.importHref() and Polymer.ready(), and adding the imports > manually in the head, now it works fine. You can check out this commit in > my project here: > https://github.com/gwidgets/gwt-polymer-starter-kit/commit/7ce3c9523e3e7955f87659f9fcc4d03ac8928a5e > > <https://github.com/gwidgets/gwt-polymer-starter-kit/commit/7ce3c9523e3e7955f87659f9fcc4d03ac8928a5e> > > If it does not work then you can open an issue, but you should now that > the project's contributors are very slow to respond... > > Le vendredi 12 août 2016 16:37:31 UTC+2, Bruno Salmon a écrit : >> >> Yes I'm using the latest gwt-polymer-elements version, so 1.2.3.0, and >> it works for me with beta1. >> >> The runtime error occurs also in production mode, not only in Dev mode. >> >> I don't call whenPolymerLoaded() directly in my code, I only use >> Polymer.ready(Element >> e, Function f) but I guess whenPolymerLoaded() is then called within the >> Vaadin implementation. >> >> Actually I just would like to know if it's a gwt-polymer-elements 1.2.3.0 >> issue (in this case I will wait Vaadin to deliver the next release that >> will work GWT 2.8.0) or if it's a GWT issue that needs to be fixed before >> 2.8.0 is out. >> >> Should I rather open an issue on the gwt-polymer-elements github project? >> >> >> On Friday, 12 August 2016 14:49:04 UTC+2, zakaria amine wrote: >>> >>> Normally, the latest version gwt-polymer-elements 1.2.3.0 is not >>> supposed to work with beta1 but with SNAPSHOT or rc1, which version are you >>> using? >>> >>> Another advise is try not use whenPolymerLoaded() in Dev mode, comment >>> it out and take out the statements inside it, use it only when deploying to >>> a server. >>> >>> >>> Le vendredi 12 août 2016 11:39:41 UTC+2, Bruno Salmon a écrit : >>>> >>>> Hi, >>>> >>>> I have a GWT Polymer Elements project that compiles and run ok with GWT >>>> 2.8.0-beta1. >>>> >>>> When switching to 2.8.0-rc1 or 2.8.0-rc2, it compiles ok but doesn't >>>> run due to the follow runtime error: >>>> >>>> Uncaught TypeError: ok_0_g$.call_1_g$ is not a function >>>> Polymer.java:159 >>>> >>>> The Polymer.java:159 line is underlined in the code below: >>>> >>>> private static native void whenPolymerLoaded(Function ok) >>>> /*-{ >>>> function done() { >>>> // Set our static reference to Base >>>> @com.vaadin.polymer.Polymer::Polymer = $wnd.Polymer; >>>> @com.vaadin.polymer.Polymer::Base = $wnd.Polymer.Base; >>>> // Polymer dynamic loaded does not remove unresolved >>>> $doc.body.removeAttribute('unresolved'); >>>> // >>>> *[email protected]::call(*)()*; >>>> } >>>> if (!$wnd.Polymer) { >>>> var l = $doc.createElement('link'); >>>> l.rel = 'import'; >>>> l.href = >>>> @com.vaadin.polymer.Polymer::absoluteHref(*)('polymer'); >>>> l.onload = done; >>>> $doc.head.appendChild(l); >>>> } else { >>>> done(); >>>> } >>>> }-*/; >>>> >>>> I don't know if this is a GWT issue or a GWT Polymer Elements issue. >>>> Any idea? >>>> >>>> Thanks. >>>> >>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
