You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Matej Knopp <ma...@gmail.com> on 2008/09/03 00:10:08 UTC
Re: Google Chrome & Wicke
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 <cs...@yahoo.com> 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@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Google Chrome & Wicke
Posted by cstein1206 <cs...@yahoo.com>.
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?
--
View this message in context: http://www.nabble.com/Google-Chrome---Wicket-tp19277005p19280167.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Google Chrome & Wicke
Posted by Wayne Pope <wa...@googlemail.com>.
>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@gmail.com
> 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
> <ha...@genietown.com> 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 <cs...@yahoo.com>
> 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 <cs...@yahoo.com>
> >>>> 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@wicket.apache.org
> >>>>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >>>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>>
> >>>>
> >>>>
> >>>
> >>> --
> >>> 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@wicket.apache.org
> >>> For additional commands, e-mail: users-help@wicket.apache.org
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >>
> >
> > --
> > 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@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
>
>
> --
> 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@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Google Chrome & Wicke
Posted by Matej Knopp <ma...@gmail.com>.
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 <be...@emc.com> 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@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Google Chrome & Wicke
Posted by lesterburlap <be...@emc.com>.
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@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Google Chrome & Wicke
Posted by Thomas Krause <th...@gmail.com>.
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
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
> <ha...@genietown.com> 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 <cs...@yahoo.com> 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 <cs...@yahoo.com>
>>>>> 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@wicket.apache.org
>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> 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@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>>
>>
>> --
>> 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@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
>
>
> --
> 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@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Google-Chrome---Wicket-tp19277005p19307870.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Google Chrome & Wicke
Posted by Martijn Dashorst <ma...@gmail.com>.
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
<ha...@genietown.com> 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 <cs...@yahoo.com> 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 <cs...@yahoo.com>
>>>> 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@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>>
>>>
>>> --
>>> 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@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>
>
> --
> 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@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
--
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@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Google Chrome & Wicke
Posted by Hassan Chafi <ha...@genietown.com>.
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 <cs...@yahoo.com> 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 <cs...@yahoo.com>
>>> 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@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>>
>>
>> --
>> 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@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
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@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Google Chrome & Wicke
Posted by Matej Knopp <ma...@gmail.com>.
Can you try that with latest trunk?
-Matej
On Wed, Sep 3, 2008 at 1:51 AM, cstein1206 <cs...@yahoo.com> 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 <cs...@yahoo.com> 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@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>
>
> --
> 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@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Google Chrome & Wicket
Posted by James Carman <ja...@carmanconsulting.com>.
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 <be...@emc.com> 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@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Google Chrome & Wicket
Posted by lesterburlap <be...@emc.com>.
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@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Google Chrome & Wicket
Posted by cstein1206 <cs...@yahoo.com>.
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 <cs...@yahoo.com> 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@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
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@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org