[
https://issues.apache.org/jira/browse/MYFACES-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899547#action_12899547
]
Werner Punz edited comment on MYFACES-2876 at 8/17/10 4:07 PM:
---------------------------------------------------------------
ok the reason why the removeChilds did not work simply was that the delete
childNode caused an objectError on ieMobile, fixed that.
Now update, insertbefore work, insertAfter fails it pushes the new node at the
bottom of the divs instead of pushing it after the updated element.
node.hasChildNodes() does not work, we have to do it the hard way via undefined
check and length check
The reason for insertafter positioning the elements wrongly is following code
nodeHolder = document.createElement("div");
parentNode = afterNode.parentNode;
parentNode.insertBefore(nodeHolder, afterNode.nextSibling);
the problem here is that IEMobile interpretes the nextSibling wrong and
delivers a totally wrong position, the insertBefore then causes internally an
appendChild.
Now this is not fixable on my part, but since the insertAfter is not really
used we can live with it. IE Mobile 7 will fix this I assume, since it is based
on a blend of IE7 and 8.
was (Author: werpu):
ok the reason why the removeChilds did not work simply was that the delete
childNode caused an objectError on ieMobile, fixed that.
Now update, insertbefore work, insertAfter fails it pushes the new node at the
bottom of the divs instead of pushing it after the updated element.
> 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.
