Open taurus227 opened 6 years ago
Thanks for reporting this, we will take a look at it. What version of Vaadin Framework are you using?
8.1.5
Do you have both
<dependency>
<groupId>com.vaadin</groupId>
<artifactId>vaadin-board-precompiled</artifactId>
<version>1.0.0</version>
</dependency>
and
<dependency>
<groupId>com.vaadin</groupId>
<artifactId>vaadin-board-precompiled</artifactId>
<version>1.0.0</version>
</dependency>
Dependencies in you pom.xml
?
Well, you mentioned the same vaadin-board-precompiled
twice. And that's the only one I added to my pom, because vaadin-board-precompiled
already depends on vaadin-board
, so both are in my dependency hierarchy.
You're right I messed with copy paste, but I meant vaadin-board
and
vaadin-board-precompiled
. We will look into this.
On Oct 4, 2017 12:02 PM, "Robert Mikes" notifications@github.com wrote:
Well, you mentioned the same vaadin-board-precompiled twice. And that's the only one I added to my pom, because vaadin-board-precompiled already depends on vaadin-board, so both are in my dependency hierarchy.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/vaadin/board/issues/117#issuecomment-334257582, or mute the thread https://github.com/notifications/unsubscribe-auth/AJXXtNTtQGJmw0MIycLoNtp5N_S2qQKEks5so9ZYgaJpZM4Pt7nZ .
I am having a similar problem with the new Firefox and the Opera browser. (Java board) My setup works fine with Chrome. The board demo site seems to run OK on Chrome, Opera and new Firefox.
Have you tested with 1.1.0-beta1? It includes some updated polyfills that improve behavior in IE and other browsers.
If this still happens, a simple example of how to reproduce this issue would really help us figuring out what's going on
I am using 1.1.0-beta1 but in an unusual setup. I have the board jar and the webcomponents-helper wrapped in an OSGi bundle and running in an OSGi framework, but not as per the Vaadin OSGi approach :-) Over the weekend I will try to isolate where the problem could be. The interesting thing is that it works OK in Chrome.
Following discussion with Artur in the board forum we have established that my problem relates to the fact that Chrome auto handles the polyfill and Firefox and Safari do not. Handling the loading of the polyfill in OSGi solved the problem in my case.
Using the Java API, on Firefox the log shows this upon login (so upon Board constructor being invoked):
Oct 05, 2017 12:45:13 AM com.vaadin.server.VaadinServlet serveStaticResourcesInVAADIN INFO: Requested resource [/VAADIN/frontend/es6/webcomponentsjs/webcomponents-lite.js] not found from filesystem or through class loader. Add widgetset and/or theme JAR to your classpath or add files to WebContent/VAADIN folder.
When selecting the View that contains the Board, the browser hangs and the page is never displyed.
Using Chrome, the page is displayed, but there are more logs:
Oct 05, 2017 12:47:49 AM com.vaadin.server.VaadinServlet serveStaticResourcesInVAADIN INFO: Requested resource [/VAADIN/frontend/es6/vaadin-board/vaadin-board.html] not found from filesystem or through class loader. Add widgetset and/or theme JAR to your classpath or add files to WebContent/VAADIN folder. Oct 05, 2017 12:47:49 AM com.vaadin.server.VaadinServlet serveStaticResourcesInVAADIN INFO: Requested resource [/VAADIN/frontend/es6/vaadin-board/vaadin-board-row.html] not found from filesystem or through class loader. Add widgetset and/or theme JAR to your classpath or add files to WebContent/VAADIN folder.