Document, blog, and draft wiki pages to describe usage, and updates
-------------------------------------------------------------------
Key: RFPL-451
URL: https://jira.jboss.org/jira/browse/RFPL-451
Project: RichFaces Planning
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Jay Balunas
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
selenium tests for smoke testing core-demo
------------------------------------------
Key: RFPL-710
URL: https://jira.jboss.org/browse/RFPL-710
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: QA
Affects Versions: 4.0.0.Milestone1
Reporter: Prabhat Jha
Assignee: Lukas Fryc
This is not going to be exhaustive because these are part of manual UI tests as well but this set of tests should verify that important features of core-demo are working.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Fix Jabber client JSF 1.2
-------------------------
Key: RFPL-368
URL: https://jira.jboss.org/jira/browse/RFPL-368
Project: RichFaces Planning
Issue Type: Task
Reporter: Lukas Fryc
Assignee: Lukas Fryc
Priority: Minor
There was found some failures in RFPL-350, ask ppitonak for detailed testing results and fix failures.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Introduce abstract DelayTester and rewrite all delay tests to use it
--------------------------------------------------------------------
Key: RFPL-1129
URL: https://issues.jboss.org/browse/RFPL-1129
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: QE
Affects Versions: 4.0.0.Milestone6
Reporter: Lukas Fryc
Assignee: Lukas Fryc
Fix For: 4.0.0.CR1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
create matrix jobs in Hudson for RF4 browser compatibility testing
-------------------------------------------------------------------
Key: RFPL-715
URL: https://jira.jboss.org/browse/RFPL-715
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: QA
Reporter: Prabhat Jha
Assignee: Lukas Fryc
P1: IE8, IE7, FF3 on Linux and Window, Chrome (latest)
P2: IE9 (even if it's beta), FF4 (even if it's beta)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Create real-world example of using nested iteration components
--------------------------------------------------------------
Key: RFPL-750
URL: https://jira.jboss.org/browse/RFPL-750
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: QA
Reporter: Lukas Fryc
Assignee: Lukas Fryc
Fix For: 4.0.0.Milestone3
Nested components are used in many scenarios, but doesn't work properly in RichFaces 4.0.0.M1.
Define real-world example of such scenario using as many combination of components not working as possible,
and then try to find workaround.
Components which doesn't work properly:
ui:repeat
rich:dataTable and other tables
rich:componentControl
clientId function
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
QE: RF-10863 should be also checked thorougly for all the components which supports client behaviors and supposed to support server side events
-----------------------------------------------------------------------------------------------------------------------------------------------
Key: RFPL-1425
URL: https://issues.jboss.org/browse/RFPL-1425
Project: RichFaces Planning
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: components
Affects Versions: 4.0.0.Final
Reporter: Ilya Shaikovsky
Assignee: Prabhat Jha
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Brian Leathem created RFPL-2265:
-----------------------------------
Summary: Update the docs to remove browser version numbers, and link to the browser compatibility matrix
Key: RFPL-2265
URL: https://issues.jboss.org/browse/RFPL-2265
Project: RichFaces Planning
Issue Type: Task
Security Level: Public (Everyone can see)
Components: doc
Reporter: Brian Leathem
Assignee: Brian Leathem
Fix For: 4.2-Tracking
The RichFaces devloper guide specifies versions of browsers against which the components are expected to work.
http://docs.jboss.org/richfaces/latest_4_X/Developer_Guide/en-US/html/cha...
This is a duplicate of the information maintined in the wiki:
https://community.jboss.org/wiki/PrioritizedRichFacesBrowsersCompatibilit...
I propose simplifying the Developer guide to list only the supported browsers, but not their versions. We would then link to the relevant wiki page from the developer guide for those looking for information on specific versions.
The alternative to this is to be more rigorous about keeping the two docs in synch with every release.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira