You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by "PALMER, THOMAS C (ATTCORP)" <TP...@att.com> on 2011/08/25 21:16:34 UTC
Problem with Android and ajax?
We have a problem with a mobile site on an Android. Basically, we're updating select options via ajax with one option that should be selected after the update completes. On an iPhone this works fine and the selected option shows in the list as selected. On Android we get nothing in the dropdown at all until the page is refreshed (reloading the complete state).
The Android user agent we're seeing ("Mozilla/5.0 (Linux; U; Android 2.1-update1; en-us; HTC-A6366/1.0 Build/ERE27) AppleWebKit/530.17 (KHTML, like Gecko) Version/4.0 Mobile Safari/530.17") will be treated as Safari based on the browser recognition code in wicket-event.js. It appears the code in wicket-ajax.js in Wicket.replaceOuterHtmlSafari isn't doing the right thing for Android, despite them both being Webkit based.
Any thoughts on a way to address this? This is wicket 1.4.14.
Thanks much -
Tom Palmer
Director, Strategic Technology Services
AT&T Hosting & Application Services | 2000 Perimeter Park Drive, Suite 140 | Morrisville, NC 27560
Office: +1 (919) 388-5937 | Mobile: +1 (919) 627-5431
thomas.palmer@att.com<ma...@att.com>
Confidentiality Notice and Disclaimer: This e-mail transmission may contain confidential and/or proprietary information of AT&T that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that AT&T can arrange for proper delivery, and then please delete the message from your inbox. Thank you.
Re: Problem with Android and ajax?
Posted by Martin Grigorov <mg...@apache.org>.
You can also try at http://wicketstuff.org/wicket14/ajax/choice
I just updated it to 1.4.18.
On Thu, Aug 25, 2011 at 10:21 PM, Pedro Santos <pe...@gmail.com> wrote:
> Hi Palmer, it is possible related to
> https://issues.apache.org/jira/browse/WICKET-3820 , upgrade to 1.4.18
>
> 2011/8/25 PALMER, THOMAS C (ATTCORP) <TP...@att.com>
>
>> We have a problem with a mobile site on an Android. Basically, we're
>> updating select options via ajax with one option that should be selected
>> after the update completes. On an iPhone this works fine and the selected
>> option shows in the list as selected. On Android we get nothing in the
>> dropdown at all until the page is refreshed (reloading the complete state).
>>
>> The Android user agent we're seeing ("Mozilla/5.0 (Linux; U; Android
>> 2.1-update1; en-us; HTC-A6366/1.0 Build/ERE27) AppleWebKit/530.17 (KHTML,
>> like Gecko) Version/4.0 Mobile Safari/530.17") will be treated as Safari
>> based on the browser recognition code in wicket-event.js. It appears the
>> code in wicket-ajax.js in Wicket.replaceOuterHtmlSafari isn't doing the
>> right thing for Android, despite them both being Webkit based.
>>
>> Any thoughts on a way to address this? This is wicket 1.4.14.
>>
>> Thanks much -
>>
>> Tom Palmer
>> Director, Strategic Technology Services
>> AT&T Hosting & Application Services | 2000 Perimeter Park Drive, Suite 140
>> | Morrisville, NC 27560
>> Office: +1 (919) 388-5937 | Mobile: +1 (919) 627-5431
>> thomas.palmer@att.com<ma...@att.com>
>>
>> Confidentiality Notice and Disclaimer: This e-mail transmission may contain
>> confidential and/or proprietary information of AT&T that is intended only
>> for the individual or entity named in the e-mail address. If you are not the
>> intended recipient, you are hereby notified that any disclosure, copying,
>> distribution, or reliance upon the contents of this e-mail is strictly
>> prohibited. If you have received this e-mail transmission in error, please
>> reply to the sender, so that AT&T can arrange for proper delivery, and then
>> please delete the message from your inbox. Thank you.
>>
>>
>
>
> --
> Pedro Henrique Oliveira dos Santos
>
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Problem with Android and ajax?
Posted by Pedro Santos <pe...@gmail.com>.
Hi Palmer, it is possible related to
https://issues.apache.org/jira/browse/WICKET-3820 , upgrade to 1.4.18
2011/8/25 PALMER, THOMAS C (ATTCORP) <TP...@att.com>
> We have a problem with a mobile site on an Android. Basically, we're
> updating select options via ajax with one option that should be selected
> after the update completes. On an iPhone this works fine and the selected
> option shows in the list as selected. On Android we get nothing in the
> dropdown at all until the page is refreshed (reloading the complete state).
>
> The Android user agent we're seeing ("Mozilla/5.0 (Linux; U; Android
> 2.1-update1; en-us; HTC-A6366/1.0 Build/ERE27) AppleWebKit/530.17 (KHTML,
> like Gecko) Version/4.0 Mobile Safari/530.17") will be treated as Safari
> based on the browser recognition code in wicket-event.js. It appears the
> code in wicket-ajax.js in Wicket.replaceOuterHtmlSafari isn't doing the
> right thing for Android, despite them both being Webkit based.
>
> Any thoughts on a way to address this? This is wicket 1.4.14.
>
> Thanks much -
>
> Tom Palmer
> Director, Strategic Technology Services
> AT&T Hosting & Application Services | 2000 Perimeter Park Drive, Suite 140
> | Morrisville, NC 27560
> Office: +1 (919) 388-5937 | Mobile: +1 (919) 627-5431
> thomas.palmer@att.com<ma...@att.com>
>
> Confidentiality Notice and Disclaimer: This e-mail transmission may contain
> confidential and/or proprietary information of AT&T that is intended only
> for the individual or entity named in the e-mail address. If you are not the
> intended recipient, you are hereby notified that any disclosure, copying,
> distribution, or reliance upon the contents of this e-mail is strictly
> prohibited. If you have received this e-mail transmission in error, please
> reply to the sender, so that AT&T can arrange for proper delivery, and then
> please delete the message from your inbox. Thank you.
>
>
--
Pedro Henrique Oliveira dos Santos