Woodstock Runs Better On Chrome, Than On Firefox 3.0

I just tested Google's Chrome browser - it looks and works really good. Especially woodstock components (created with Netbeans 6.0/6.5) are rendered fast and correctly. I had trouble with Firefox 3.0 - most of the woodstock components were rendered (even visible) after several reloads of the whole page...


Web Apps, SPA, PWA with vanilla Java Script (ES 6+), CSS 3 and WebStandards only. As simple as possible, but not simpler. See you at: (Progressive) Web apps, Single Page Apps and WebStandards airhacks workshops at MUC airport, Winter Edition

airhacks.fm the podcast:

Stay in touch: airhacks.news.

Comments:

chrome uses webkit which is a pretty mature web content renderer but I noticed some glitches e.g javafx.com was not rendered properly.

chrome would probably make it to my favourite browser but the license is a showstopper for me.

(it imported the java 6.10 plugin from firefox applets worked - pretty cool)

Posted by mbien on September 04, 2008 at 01:01 PM CEST #

It's a shame for Woodstock to fail on such an important browser like Firefox - at least the project demo pages for some components still have problems with Firefox.

Chrome has fixed nothing at Woodstock, your headline is misleading.

Posted by jiai on September 04, 2008 at 01:50 PM CEST #

Jiai,

"...It's a shame for Woodstock to fail on such an important browser like Firefox..."

Woodstock fails "only" on the newest Firefox 3.0. I had no time to investigate the reason yet.

"Chrome has fixed nothing at Woodstock, your headline is misleading."

Actually you are right. It was a really spontaneous post after some tests...

thank you for your comment,

regards,

adam

Posted by Adam Bien on September 04, 2008 at 04:34 PM CEST #

Jiai,

I changed the headline - now should be better :-),

regards,

adam

Posted by Adam Bien on September 04, 2008 at 04:35 PM CEST #

Great... too bad it currently appears as if woodstock is going to die a slow death since it has been abandoned by the development team.

Posted by Jeff on September 04, 2008 at 04:52 PM CEST #

"Woodstock fails "only" on the newest Firefox 3.0. I had no time to investigate the reason yet."

Yes indeed, Firefox 3.0 "only" but nearly every Firefox 2.0 will be replaced by 3.0 in the next few weeks (the automatic update offers it) ....

<irony>And Firefox 3.0 has fallen down from heaven, there where no betas on which Woodstock could have been tested.</irony>

I think you don't have to investigate it - it is documented in the issues list and seems to be partly solved (but not in every case)?!? The latest published build is "Not Fully Qualified"...

Posted by 91.4.88.93 on September 04, 2008 at 11:22 PM CEST #

Sorry, I've forgotten to post my name.

Posted by jiai on September 04, 2008 at 11:25 PM CEST #

As far as I know, Woostock has difficulties with the way Firefox 3 loads JavaScript. That's why some components are not rendered properly or not at all.
Unfortunately, Woodstock is not really evolving at the moment and the developers do not communicate a lot about future plans.
I can see IceFaces and RichFaces waving from the fast lane.

Posted by Stefan Bley on October 01, 2008 at 07:01 PM CEST #

For those who are interested:
Woodstock development has been stopped. The last version to be released by Sun is Woodstock 4.2.
http://www.nabble.com/Woodstock-update-td20317701.html

Posted by Stefan Bley on November 06, 2008 at 12:36 PM CET #

Post a Comment:
  • HTML Syntax: NOT allowed
Online Workshops
realworldpatterns.com
...the last 150 posts
...the last 10 comments
License