RichFacesQA

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Metamer: *changeListeners refactored with phaseInfo

Metamer: *changeListeners refactored with phaseInfo

Conflicts:

metamer/ftest/src/test/java/org/richfaces/tests/metamer/ftest/richItemChangeListener/AbstractItemChangeListenerTest.java

metamer/ftest/src/test/java/org/richfaces/tests/metamer/ftest/richPanelToggleListener/AbstractPanelToggleListenerTest.java

metamer/ftest/src/test/java/org/richfaces/tests/metamer/ftest/richTreeSelectionChangeListener/AbstractTreeSelectionChangeListenerTest.java

metamer/ftest/src/test/java/org/richfaces/tests/metamer/ftest/richTreeToggleListener/AbstractTreeToggleListenerTest.java

Fixes for rich:isUserInRole() (PBR-460)

Fixes for rich:isUserInRole() (PBR-460)

Remove extra h:form

h:form is defined in the template around where the "component" is inserted, adding another h:form inside the define for "component" results in a form within a form that are essentially identical and two java.faces.encodedURL form params are created and passed with Request

Remove extra h:form

h:form is defined in the template around where the "component" is inserted, adding another h:form inside the define for "component" results in a form within a form that are essentially identical and two java.faces.encodedURL form params are created and passed with Request

Remove extra h:form

h:form is defined in the template around where the "component" is inserted, adding another h:form inside the define for "component" results in a form within a form that are essentially identical and two java.faces.encodedURL form params are created and passed with Request

Remove extra h:form

h:form is defined in the template around where the "component" is inserted, adding another h:form inside the define for "component" results in a form within a form that are essentially identical and two java.faces.encodedURL form params are created and passed with Request

Merge remote-tracking branch 'origin/4.2.x' into wfk21

RF-12421: menuGroup in dropDownMenu does not work when rich:messages presents

Created test page wich copies exactly showcase example, added user

defined footer with rich:messages - issue did not reproduced.

reload testers refactored

reload testers refactored

Conflicts:

metamer/ftest/src/test/java/org/richfaces/tests/metamer/ftest/richCalendar/TestRichCalendarKVS.java

reload testers refactored

reload testers refactored

Conflicts:

metamer/ftest/src/test/java/org/richfaces/tests/metamer/ftest/richCalendar/TestRichCalendarKVS.java

2 tests for autocomplete stabilized

2 tests for autocomplete stabilized

2 tests for autocomplete stabilized

2 tests for autocomplete stabilized

testRender for command link and command button fixed

testRender for command link and command button fixed

testRender for command link and command button fixed

testRender for command link and command button fixed

Metamer: rich:inplaceInput: tests for JS API

Metamer: rich:inplaceInput: tests for JS API

Metamer: rich:inplaceInput: tests for JS API

Metamer: rich:inplaceInput: tests for JS API

RF-12548: rich:tabPanel does not work after ajax request

Reproducing for 4.3.0.M1 and myfaces. It is not occuring.

Metamer: rich:inplaceInput: added missing tests for some attributes

Metamer: rich:inplaceInput: added missing tests for some attributes

Page fragments: renamed inplaceInput component