[
https://issues.apache.org/jira/browse/MYFACES-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898978#action_12898978
]
Werner Punz edited comment on MYFACES-2876 at 8/16/10 3:09 PM:
---------------------------------------------------------------
Next issue, following construct makes the winmobile browser fail
onclick="javax.faces.request(this, event, ....)"
the issue here is that ie does not pass an event object but instead relies in
window event, to make the code work the follwing code has to be passe ddown
onclick="javax.faces.request(this, ('undefined' == typeof event)? window.event:
event, ....)"
We probably have to fix that on the f:ajax level in the long run for now it is
not that important.
ok calls into dom fuzzyFormDetection fail, not sure why, the method is not
there, other classes which use the singletonExtend construct have all methods
intact, has to be further investigated
Ok the issue was the onload handler in the dom constructor for the auto eval
detection, seems like winMobile hates onload, since this is the only handler we
have I can live with not having it for winmobile.
Seems like after the onload handler the ajax request is triggered properly, my
eval testcase which is the simplest one not doing any heavy dom modifications
now is running through.
I wont commit the code today anymore, maybe by the end of the week, I want to
get this as far as possible first.
was (Author: werpu):
Next issue, following construct makes the winmobile browser fail
onclick="javax.faces.request(this, event, ....)"
the issue here is that ie does not pass an event object but instead relies in
window event, to make the code work the follwing code has to be passe ddown
onclick="javax.faces.request(this, ('undefined' == typeof event)? window.event:
event, ....)"
We probably have to fix that on the f:ajax level in the long run for now it is
not that important.
ok calls into dom fuzzyFormDetection fail, not sure why, the method is not
there, other classes which use the singletonExtend construct have all methods
intact, has to be further investigated
Ok the issue was the onload handler in the dom constructor for the auto eval
detection, seems like winMobile hates onload, since this is the only handler we
have I can live with not having it for winmobile.
> Ajax Support in Mobile Browsers
> -------------------------------
>
> Key: MYFACES-2876
> URL: https://issues.apache.org/jira/browse/MYFACES-2876
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 2.0.0-beta
> Environment: Windows Mobile 6.1, Blackberry 4.7
> Reporter: Mamallan Uthaman
>
> In Windows Mobile (WM) 6.1 platform, <f:ajax> is converted into a full-page
> submit instead of a PPR. The reason is unlike Webkit based mobile-browsers,
> WM 6.1 or Blackberry (BB) 4.7 offers only a limited JavaScript-DOM support,
> so we need to optimize MyFaces's Ajax mechanism to work around the
> limitations of mobile browsers. I used the sample code below for testing.
> Facelets code:
> <h:commandButton value="PPR">
> <f:ajax event="action" render="second"/>
> </h:commandButton>
> <h:outputText value="#{item.date.seconds}" id="second"/>
> Item.Java:
> import java.util.Date;
> public class Item {
> Date date;
> public void setDate(Date date) {
> this.date = date;
> }
> public Date getDate() {
> return new Date();
> }
> }
> faces-config:
> <managed-bean>
> <managed-bean-name>item</managed-bean-name>
> <managed-bean-class>Item</managed-bean-class>
> <managed-bean-scope>request</managed-bean-scope>
> </managed-bean>
> Also, in the case of BB 4.7 , <f:ajax> can successfully send a PPR, but PPR
> response is ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
