[JBoss JIRA] Created: (RF-11272) rich:collapsiblePanel the collapse functionality does not work when it is in Ajax mode
by Juraj Huska (JIRA)
rich:collapsiblePanel the collapse functionality does not work when it is in Ajax mode
--------------------------------------------------------------------------------------
Key: RF-11272
URL: https://issues.jboss.org/browse/RF-11272
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: showcase
Affects Versions: 4.1.0.Milestone1
Environment: richfaces-showcase-4.1.0.20110805-M1-jee6.war
container - JBoss AS 6.0.0.Final
browser - IE 9
Reporter: Juraj Huska
In demo for rich:collapsiblePanel, it is not possible to collapse the panel in the example which is in Ajax mode. Clicking on the part of panel which should collapse the panel simply does nothing. The expand functionality of this panel works fine, but after expanding collapse is not possible.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (RF-10862) Autocomplete: does not perform decode of the behaviors
by Ilya Shaikovsky (JIRA)
Autocomplete: does not perform decode of the behaviors
------------------------------------------------------
Key: RF-10862
URL: https://issues.jboss.org/browse/RF-10862
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 4.0.0.Final
Reporter: Ilya Shaikovsky
http://community.jboss.org/message/598526#598526
checked with
<rich:autocomplete mode="cachedAjax" tokens=", " minChars="0"
autoFill="false" selectFirst="false"
autocompleteMethod="#{autocompleteBean.autocomplete}" valueChangeListener="#{autocompleteBean.vcl}">
<a4j:ajax listener="#{autocompleteBean.list}" event="change"/>
</rich:autocomplete>
<h:inputText>
<a4j:ajax listener="#{autocompleteBean.list}" event="change"/>
</h:inputText>
input calls listener and autocomplete not. Text renderer performs String clientId = decodeBehaviors(context, component);
and in autocomplete there is no such code.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (RF-11060) onselectionchange working incorrect with two extendedDataTable on same page
by Tom Giberius (JIRA)
onselectionchange working incorrect with two extendedDataTable on same page
---------------------------------------------------------------------------
Key: RF-11060
URL: https://issues.jboss.org/browse/RF-11060
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.0.0.Final
Environment: GlassFish 3.0.1, Firefox
Reporter: Tom Giberius
Priority: Critical
If you put two extendedDataTable A en B on the same page then the following goes wrong:
If you selected record one of Table A en then select record one from table B then the onselectionchange trigger does not fire. The same counts for record two, three, etc.
This prevents me for building a Master-Detail data entry screen where both the master and the detail are multirecord. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in details, then go back to record 3 of master and then the onselectionchange trigger does not fire. The master tables "thinks" that record three is the selected record while actually it should be record one which was the selected record in the master table.
The correct behaviour should be that each table should "rember" it selected record. E.g.
Step 1) Select records one in master and show it details.
Step 2) Select record three in detail, then go back to record 3 of master and the onselectionchange of the master should fire so that details of master record 3 can be shown. If you would have go back to record one of the master then not firing the onselectionchange would be correct.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (RF-11333) rich:column sorting runs one step behind when partial state saving is disabled
by Bauke Scholtz (JIRA)
rich:column sorting runs one step behind when partial state saving is disabled
------------------------------------------------------------------------------
Key: RF-11333
URL: https://issues.jboss.org/browse/RF-11333
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.0.0.Final
Environment: Mojarra 2.1.2, Tomcat 7.0.19 / GlassFish 3.1 / JBoss AS 6.0.0, Eclipse Helios SR1, Win7 x64.
Reporter: Bauke Scholtz
The {{rich:column}} sorting runs one step behind when partial state saving is disabled by
{code}
<context-param>
<param-name>javax.faces.PARTIAL_STATE_SAVING</param-name>
<param-value>false</param-value>
</context-param>
{code}
First click on a sorting header has no effect. Any next click on an arbitrary sorting header executes the sorting as desired by the previous click.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (RF-10892) components listed in the description were quite difficult to hit
by Juraj Huska (JIRA)
components listed in the description were quite difficult to hit
----------------------------------------------------------------
Key: RF-10892
URL: https://issues.jboss.org/browse/RF-10892
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: mobile
Affects Versions: 4.0.0.Final
Reporter: Juraj Huska
Priority: Minor
1.The numbers of pages on dataScroller, mainly when there is lot of other clickable components - iPhone
2.The plus sign in the trees, mainly not the first level plus sign, but some sublevels plus signs - Nexus
3.The cross, which should cancel the poppup modal panel. iPhone, iPad
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months