[
https://issues.apache.org/jira/browse/MYFACES-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898948#action_12898948
]
Werner Punz edited comment on MYFACES-2876 at 8/16/10 10:46 AM:
----------------------------------------------------------------
Ok I have finally managed to install the device emulator for WinMobile6 and I
will put my findings here.
The good news is, the entire inheritance and delegation part runs out of the
box.
The bad news is, IE Mobile does not allow innerHTML on detached dom nodes.
This is inheritly evil because I use this techniques to bypass some IE bugs in
the first case dealing with swallowing script tags if innerHTML is applied.
Outside of that as it seems there is no setAttribute, while IE6 has provided it
for some settings.
So what we have here is a classical chicken and egg situation we have a fix for
IE which was just introduced because IE again had a bug in an area which breaks
in another version of IE.
My personal guess is we have to deal with WinMobile 6 in a separate way than
with IE6 standalone in this area.
(the entire outer HTML part is affacted in Dom.JS)
So the first step probably will be to alter the browser detection code to check
if it is winmobile 6 or plain ie6
--Done winmobile detection code added to Runtime.js also the ExtLang logger now
works which should make things easier
was (Author: werpu):
Ok I have finally managed to install the device emulator for WinMobile6 and
I will put my findings here.
The good news is, the entire inheritance and delegation part runs out of the
box.
The bad news is, IE Mobile does not allow innerHTML on detached dom nodes.
This is inheritly evil because I use this techniques to bypass some IE bugs in
the first case dealing with swallowing script tags if innerHTML is applied.
Outside of that as it seems there is no setAttribute, while IE6 has provided it
for some settings.
So what we have here is a classical chicken and egg situation we have a fix for
IE which was just introduced because IE again had a bug in an area which breaks
in another version of IE.
My personal guess is we have to deal with WinMobile 6 in a separate way than
with IE6 standalone in this area.
(the entire outer HTML part is affacted in Dom.JS)
So the first step probably will be to alter the browser detection code to check
if it is winmobile 6 or plai ie6
> 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.
