[
https://issues.jboss.org/browse/RF-12715?page=com.atlassian.jira.plugin.s...
]
Brian Leathem commented on RF-12715:
------------------------------------
I don't believe we will be able to do this check reliably on the client-side, as there
is not portable marker that an HTML element belongs to a JSF component (perhaps we should
file a spec issue asking for this).
I removing the searchForComponentRoortOrReturn method, and instead do the event re-mapping
server side, as described [in this forum
post|https://community.jboss.org/message/628872#628872].
richfaces.js searchForComponentRootOrReturn doesn't recognize
non-richfaces components
--------------------------------------------------------------------------------------
Key: RF-12715
URL:
https://issues.jboss.org/browse/RF-12715
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: component-a4j-core
Affects Versions: 4.3.0.CR1
Reporter: Brian Leathem
Priority: Blocker
Labels: regression
Fix For: 4.3.0.CR1
Original Estimate: 1 hour
Remaining Estimate: 1 hour
The searchForComponentRootOrReturn function in richfaces.js was created to correct the
source element of jsf events to jsf components. However the check of whether an element
belongs to a component fails for non JSF components.
A concrete example of this failure can be seen when an event generates from a nested
_f:ajax_ tag.
--
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