[
https://issues.jboss.org/browse/RF-12989?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-12989:
------------------------------------
Having looked at the [relevant
commit|https://github.com/richfaces4/components/commit/e6939c36ffc56661df...],
I can see that prior to RF 4.3.0, the name would default to the component id, whereas
after RF 4.3.0, the name defaults to the clientId.
So it *should* still be possible to not use a name, and only use an id, but any further
checks/manipulations would have to use the clientId, rather than the id.
When you say "the page does not work anymore", what do you mean? What
functionality breaks?
Documentation for togglePanelItem is wrong and 4.2.2 components are
not working anymore in 4.3.0.Final
------------------------------------------------------------------------------------------------------
Key: RF-12989
URL:
https://issues.jboss.org/browse/RF-12989
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: doc
Affects Versions: 4.3.0.Final
Environment: JBossAS 7.1.1
Reporter: Andrea Martino
Assignee: Brian Leathem
Priority: Minor
Labels: togglePanel
Fix For: 4.3.4
Original Estimate: 1 hour
Remaining Estimate: 1 hour
In RichFaces 4.2.2 it was possible to define togglePane items using id as attribute, as
following {code}<rich:togglePanelItem id="item1">{code}
With RichFaces 4.3.0 the page does not work anymore, I had to change the attribute to
name {code}<rich:togglePanelItem name="item1">{code}
The docs still say id is valid, even when it's not
[
http://docs.jboss.org/richfaces/latest_4_3_X/Component_Reference/en-US/ht...].
Either the docs should be changed or id attribute should be accepted as it was before.
--
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