[
https://issues.jboss.org/browse/RF-12250?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč edited comment on RF-12250 at 11/20/12 12:45 PM:
------------------------------------------------------------
The behavior can be reproduced on all WebKit devices (including desktop browsers), with
slightly modified steps to reproduce:
1. open
http://localhost:8080/jboss-as-kitchensink-rf/ on desktop
2. open
http://xyz:8080/jboss-as-kitchensink-rf/ on mobile device
3. click on {{List Members}}
4. add new member from desktop
5. new member added on mobile
6. click on {{Home}}
7. click on {{List Members}} again
8. add new member from desktop
FAIL: mobile device is not updated
was (Author: lfryc):
The behavior can be reproduced on all WebKit devices (including desktop browsers),
with slightly modified steps to reproduce:
1. open
http://localhost:8080/jboss-as-kitchensink-rf/ on desktop
2. open
http://xyz:8080/jboss-as-kitchensink-rf/ on mobile device
3. click on {{List Members}}
4. add new member from desktop
5. new member added on mobile
6. click on {{Home}}
7. click on {{List Members}} again
8. add new member from desktop
FAIL: mobile device is not updates
kitchensink archetype - creating new member from iPhone causes broken
push update on mobile devices
---------------------------------------------------------------------------------------------------
Key: RF-12250
URL:
https://issues.jboss.org/browse/RF-12250
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: archetype, component-push/poll, mobile
Affects Versions: 4.2.2.Final
Environment: iPhone, Motorola Xoom
application container: JBoss AS 7.1.1.Final.
Reporter: Juraj Húska
Assignee: Lukáš Fryč
Fix For: 4.2.5, 4.3.0.M3
Creating a new member from iPhone device causes that update on mobile devices does not
work properly. The list of new members is not updated anymore, even when creating a new
members from desktop browsers.
No error is thrown either on server or client side.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira