|
»
»
Google Chrome & Wicket
|
View:
New views
16 Messages
—
Rating Filter:
Alert me
|
 |
Google Chrome & Wicket
by jWeekend
::
Rate this Message:
I have just installed Google Chrome (v0.2.149.27).
I expect this is a browser that will be supported (eventually), so it's probably a good idea to keep a list of issues in one place (here, on the Wiki or Jira) as we come across unexpected or different behaviour of our Wicket apps. To get the ball rolling, the jWeekend "Add To Cart" button on our course booking page, that works well in all other browsers we have tried it in, is doing nothing in Google Chrome. The rest of the Ajax functionality tested so far seems to be OK. I'll send an update once I've had chance to run in development mode. Regards - Cemal http://jWeekend.co.uk |
|
|
Re: Google Chrome & Wicket
by cstein1206
::
Rate this Message:
I have installed Google Chrome as well and found several Wicket extensions not working, namely
- modal window - tabbed panels - editable label - clock example Maybe it's a bit too early for Chrome... |
|
|
Re: Google Chrome & Wicke
by Matej Knopp
::
Rate this Message:
Modal window seems to work fine for me, except that events are not
propagated when mouse is over iframe. Tabbed panel works fine, so does editable label and clock example. (tested with latest 1.4 examples) -Matej On Tue, Sep 2, 2008 at 11:53 PM, cstein1206 <cstein1206@...> wrote: > > I have installed Google Chrome as well and found several Wicket extensions > not working, namely > - modal window > - tabbed panels > - editable label > - clock example > > Maybe it's a bit too early for Chrome... > -- > View this message in context: http://www.nabble.com/Google-Chrome---Wicket-tp19277005p19279190.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Google Chrome & Wicke
by cstein1206
::
Rate this Message:
I've been using 1.4-m3 and things don't work here with Google Chrome 0.2.149.27. Is there a newer version of those examples I didn't see?
|
|
|
Re: Google Chrome & Wicket
by cstein1206
::
Rate this Message:
That's weird since I don't get anything (examples are from 1.4-m3). For me it seems like Chrome is handling the AJAX responses differently as it's always reporting 0 characters in the response.
Here's the full debug output of the modal window from Chrome when clicking on "Show modal dialog with a page": INFO: Using XMLHttpRequest transport INFO: INFO: Initiating Ajax GET request on ?wicket:interface=:1:showModal1::IBehaviorListener:0:&random=0.8373860055580735 INFO: Invoking pre-call handler(s)... INFO: Received ajax response (0 characters) INFO: ERROR: Error while parsing response: Could not find root <ajax-response> element INFO: Invoking post-call handler(s)... INFO: Invoking failure handler(s)... HTH -Chris
|
|
|
Re: Google Chrome & Wicke
by Matej Knopp
::
Rate this Message:
Can you try that with latest trunk?
-Matej On Wed, Sep 3, 2008 at 1:51 AM, cstein1206 <cstein1206@...> wrote: > > That's weird since I don't get anything (examples are from 1.4-m3). For me it > seems like Chrome is handling the AJAX responses differently as it's always > reporting 0 characters in the response. > Here's the full debug output of the modal window from Chrome when clicking > on "Show modal dialog with a page": > > INFO: Using XMLHttpRequest transport > INFO: > INFO: Initiating Ajax GET request on > ?wicket:interface=:1:showModal1::IBehaviorListener:0:&random=0.8373860055580735 > INFO: Invoking pre-call handler(s)... > INFO: Received ajax response (0 characters) > INFO: > ERROR: Error while parsing response: Could not find root <ajax-response> > element > INFO: Invoking post-call handler(s)... > INFO: Invoking failure handler(s)... > > HTH > -Chris > > > Matej Knopp-2 wrote: >> >> Modal window seems to work fine for me, except that events are not >> propagated when mouse is over iframe. >> Tabbed panel works fine, so does editable label and clock example. >> >> (tested with latest 1.4 examples) >> >> -Matej >> >> On Tue, Sep 2, 2008 at 11:53 PM, cstein1206 <cstein1206@...> wrote: >>> >>> I have installed Google Chrome as well and found several Wicket >>> extensions >>> not working, namely >>> - modal window >>> - tabbed panels >>> - editable label >>> - clock example >>> >>> Maybe it's a bit too early for Chrome... >>> -- >>> View this message in context: >>> http://www.nabble.com/Google-Chrome---Wicket-tp19277005p19279190.html >>> Sent from the Wicket - User mailing list archive at Nabble.com. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> >> > > -- > View this message in context: http://www.nabble.com/Google-Chrome---Wicket-tp19277005p19280602.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
|
|
|
Re: Google Chrome & Wicket
by Timo Rantalaiho
::
Rate this Message:
On Wed, 03 Sep 2008, Chris Stein wrote:
> I was trying to follow Matej's suggestion and build the latest version from trunk. To just try it out, it's easier to use the readymade snapshot jars from the snapshot maven repository hosted at wicketstuff.org. Best wishes, Timo -- Timo Rantalaiho Reaktor Innovations Oy <URL: http://www.ri.fi/ > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Google Chrome & Wicket
by lesterburlap
::
Rate this Message:
I'm getting the same "Received ajax response (0 characters)" / "Error while parsing response: Could not find root <ajax-response> element" message in the ajax debug window. We're using 1.3.4. Our application is totally inoperable in Chrome. I'm not worrying too much, though, since Chrome is still beta, but am curious how this works out... LBB |
|
|
Re: Google Chrome & Wicke
by Hassan Chafi
::
Rate this Message:
I tried the browser on our own production code, and it doesn't work on pages that use wicket ajax heavily.
I actually tried it on http://wicketstuff.org/wicket13/ajax/modal-window and it doesn't work their either. Even if does work on 1.4, I think depending on when this thing releases, 1.3 has to support it. Now It may be that Google has to fix their browser as I heard that even salesforce.com is not working with Chrome.
|
|
|
Re: Google Chrome & Wicket
by jwcarman
::
Rate this Message:
They said that they prioritize which sites they test Chrome with based
on google searches. So, everyone google for Wicket examples! On Wed, Sep 3, 2008 at 5:34 PM, lesterburlap <beach_nathan@...> wrote: > > > I'm getting the same "Received ajax response (0 characters)" / "Error while > parsing response: Could not find root <ajax-response> element" message in > the ajax debug window. We're using 1.3.4. > > Our application is totally inoperable in Chrome. I'm not worrying too much, > though, since Chrome is still beta, but am curious how this works out... > > LBB > -- > View this message in context: http://www.nabble.com/Google-Chrome---Wicket-tp19277005p19298676.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Google Chrome & Wicke
by Martijn Dashorst
::
Rate this Message:
Can we please get serious here? Google has delivered a beta product.
Untested, full with bugs. While I'd like to make sure that our framework runs great on Chrome, I really like to wait until google gets their act together and fix their f*ing product before we commit resources to fix bugs that won't make it into the final product. There are more important things to do than to clean up Google's mess. Martijn On Thu, Sep 4, 2008 at 12:44 AM, Hassan Chafi <hassan.chafi@...> wrote: > > I tried the browser on our own production code, and it doesn't work on pages > that use wicket ajax heavily. > > I actually tried it on http://wicketstuff.org/wicket13/ajax/modal-window and > it doesn't work their either. > > Even if does work on 1.4, I think depending on when this thing releases, 1.3 > has to support it. Now It may be that Google has to fix their browser as I > heard that even salesforce.com is not working with Chrome. > > > > Matej Knopp-2 wrote: >> >> Can you try that with latest trunk? >> >> -Matej >> >> On Wed, Sep 3, 2008 at 1:51 AM, cstein1206 <cstein1206@...> wrote: >>> >>> That's weird since I don't get anything (examples are from 1.4-m3). For >>> me it >>> seems like Chrome is handling the AJAX responses differently as it's >>> always >>> reporting 0 characters in the response. >>> Here's the full debug output of the modal window from Chrome when >>> clicking >>> on "Show modal dialog with a page": >>> >>> INFO: Using XMLHttpRequest transport >>> INFO: >>> INFO: Initiating Ajax GET request on >>> ?wicket:interface=:1:showModal1::IBehaviorListener:0:&random=0.8373860055580735 >>> INFO: Invoking pre-call handler(s)... >>> INFO: Received ajax response (0 characters) >>> INFO: >>> ERROR: Error while parsing response: Could not find root <ajax-response> >>> element >>> INFO: Invoking post-call handler(s)... >>> INFO: Invoking failure handler(s)... >>> >>> HTH >>> -Chris >>> >>> >>> Matej Knopp-2 wrote: >>>> >>>> Modal window seems to work fine for me, except that events are not >>>> propagated when mouse is over iframe. >>>> Tabbed panel works fine, so does editable label and clock example. >>>> >>>> (tested with latest 1.4 examples) >>>> >>>> -Matej >>>> >>>> On Tue, Sep 2, 2008 at 11:53 PM, cstein1206 <cstein1206@...> >>>> wrote: >>>>> >>>>> I have installed Google Chrome as well and found several Wicket >>>>> extensions >>>>> not working, namely >>>>> - modal window >>>>> - tabbed panels >>>>> - editable label >>>>> - clock example >>>>> >>>>> Maybe it's a bit too early for Chrome... >>>>> -- >>>>> View this message in context: >>>>> http://www.nabble.com/Google-Chrome---Wicket-tp19277005p19279190.html >>>>> Sent from the Wicket - User mailing list archive at Nabble.com. >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscribe@... >>>>> For additional commands, e-mail: users-help@... >>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: users-unsubscribe@... >>>> For additional commands, e-mail: users-help@... >>>> >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Google-Chrome---Wicket-tp19277005p19280602.html >>> Sent from the Wicket - User mailing list archive at Nabble.com. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscribe@... >>> For additional commands, e-mail: users-help@... >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@... >> For additional commands, e-mail: users-help@... >> >> >> > > -- > View this message in context: http://www.nabble.com/Google-Chrome---Wicket-tp19277005p19299760.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
|
|
Re: Google Chrome & Wicke
by Wayne Pope-2
::
Rate this Message:
>There are more important things to do than to clean up Google's mess.
Indeed. Why does the world go crazy over googles never completed software. Why do we have to bend over to their ever whim. I hate Google - they are a very dangerous company, which huge resources and an unfair strangle hold on the 'net. Yes they have done some good things, but they seem to get away with murder these days. On Thu, Sep 4, 2008 at 9:10 AM, Martijn Dashorst <martijn.dashorst@... > wrote: > Can we please get serious here? Google has delivered a beta product. > Untested, full with bugs. While I'd like to make sure that our > framework runs great on Chrome, I really like to wait until google > gets their act together and fix their f*ing product before we commit > resources to fix bugs that won't make it into the final product. > > There are more important things to do than to clean up Google's mess. > > Martijn > > On Thu, Sep 4, 2008 at 12:44 AM, Hassan Chafi > <hassan.chafi@...> wrote: > > > > I tried the browser on our own production code, and it doesn't work on > pages > > that use wicket ajax heavily. > > > > I actually tried it on http://wicketstuff.org/wicket13/ajax/modal-windowand > > it doesn't work their either. > > > > Even if does work on 1.4, I think depending on when this thing releases, > 1.3 > > has to support it. Now It may be that Google has to fix their browser as > I > > heard that even salesforce.com is not working with Chrome. > > > > > > > > Matej Knopp-2 wrote: > >> > >> Can you try that with latest trunk? > >> > >> -Matej > >> > >> On Wed, Sep 3, 2008 at 1:51 AM, cstein1206 <cstein1206@...> > wrote: > >>> > >>> That's weird since I don't get anything (examples are from 1.4-m3). For > >>> me it > >>> seems like Chrome is handling the AJAX responses differently as it's > >>> always > >>> reporting 0 characters in the response. > >>> Here's the full debug output of the modal window from Chrome when > >>> clicking > >>> on "Show modal dialog with a page": > >>> > >>> INFO: Using XMLHttpRequest transport > >>> INFO: > >>> INFO: Initiating Ajax GET request on > >>> > ?wicket:interface=:1:showModal1::IBehaviorListener:0:&random=0.8373860055580735 > >>> INFO: Invoking pre-call handler(s)... > >>> INFO: Received ajax response (0 characters) > >>> INFO: > >>> ERROR: Error while parsing response: Could not find root > <ajax-response> > >>> element > >>> INFO: Invoking post-call handler(s)... > >>> INFO: Invoking failure handler(s)... > >>> > >>> HTH > >>> -Chris > >>> > >>> > >>> Matej Knopp-2 wrote: > >>>> > >>>> Modal window seems to work fine for me, except that events are not > >>>> propagated when mouse is over iframe. > >>>> Tabbed panel works fine, so does editable label and clock example. > >>>> > >>>> (tested with latest 1.4 examples) > >>>> > >>>> -Matej > >>>> > >>>> On Tue, Sep 2, 2008 at 11:53 PM, cstein1206 <cstein1206@...> > >>>> wrote: > >>>>> > >>>>> I have installed Google Chrome as well and found several Wicket > >>>>> extensions > >>>>> not working, namely > >>>>> - modal window > >>>>> - tabbed panels > >>>>> - editable label > >>>>> - clock example > >>>>> > >>>>> Maybe it's a bit too early for Chrome... > >>>>> -- > >>>>> View this message in context: > >>>>> > http://www.nabble.com/Google-Chrome---Wicket-tp19277005p19279190.html > >>>>> Sent from the Wicket - User mailing list archive at Nabble.com. > >>>>> > >>>>> > >>>>> --------------------------------------------------------------------- > >>>>> To unsubscribe, e-mail: users-unsubscribe@... > >>>>> For additional commands, e-mail: users-help@... > >>>>> > >>>>> > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: users-unsubscribe@... > >>>> For additional commands, e-mail: users-help@... > >>>> > >>>> > >>>> > >>> > >>> -- > >>> View this message in context: > >>> http://www.nabble.com/Google-Chrome---Wicket-tp19277005p19280602.html > >>> Sent from the Wicket - User mailing list archive at Nabble.com. > >>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: users-unsubscribe@... > >>> For additional commands, e-mail: users-help@... > >>> > >>> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscribe@... > >> For additional commands, e-mail: users-help@... > >> > >> > >> > > > > -- > > View this message in context: > http://www.nabble.com/Google-Chrome---Wicket-tp19277005p19299760.html > > Sent from the Wicket - User mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscribe@... > > For additional commands, e-mail: users-help@... > > > > > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com > Apache Wicket 1.3.4 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > |
|
|
Re: Google Chrome & Wicke
by Thomas Krause
::
Rate this Message:
I'm quite sure it is a chrome problem. Wicket AJAX really works in *every* modern browser.
I sent a bug report to them: http://code.google.com/p/chromium/issues/detail?id=1085
|
|
|
Re: Google Chrome & Wicke
by lesterburlap
::
Rate this Message:
This is the related section of wicket-ajax.js (~line 985 in 1.3.4) right before that error message is logged. I can't find much of anything on the Internet about Chrome or WebKit supporting DOMParser, so that may be it...?
// parse the response if the callback needs a DOM tree if (this.parseResponse == true) { var xmldoc; if (typeof(window.XMLHttpRequest) != "undefined" && typeof(DOMParser) != "undefined") { var parser = new DOMParser(); xmldoc = parser.parseFromString(responseAsText, "text/xml"); } else if (window.ActiveXObject) { xmldoc = t.responseXML; } // invoke the loaded callback with an xml document this.loadedCallback(xmldoc); } else { // invoke the loaded callback with raw string this.loadedCallback(responseAsText); } |
|
|
Re: Google Chrome & Wicke
by Matej Knopp
::
Rate this Message:
Safari supports DOMParser since 2.0.1, thus both WebKit and Chrome
(which uses WebKit) support that as well. -Matej On Thu, Sep 4, 2008 at 5:26 PM, lesterburlap <beach_nathan@...> wrote: > > This is the related section of wicket-ajax.js (~line 985 in 1.3.4) right > before that error message is logged. I can't find much of anything on the > Internet about Chrome or WebKit supporting DOMParser, so that may be it...? > > // parse the response if the callback needs a DOM tree > if (this.parseResponse == true) { > var xmldoc; > if (typeof(window.XMLHttpRequest) != "undefined" && typeof(DOMParser) != > "undefined") { > var parser = new DOMParser(); > xmldoc = parser.parseFromString(responseAsText, "text/xml"); > } else if (window.ActiveXObject) { > xmldoc = t.responseXML; > } > // invoke the loaded callback with an xml document > this.loadedCallback(xmldoc); > } else { > // invoke the loaded callback with raw string > this.loadedCallback(responseAsText); > } > -- > View this message in context: http://www.nabble.com/Google-Chrome---Wicket-tp19277005p19312785.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@... > For additional commands, e-mail: users-help@... > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@... For additional commands, e-mail: users-help@... |
| Free embeddable forum powered by Nabble | Forum Help |
