[ 
https://jira.jboss.org/jira/browse/RF-7700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Kennard updated RF-7700:
--------------------------------

    Attachment: suggestion31.zip


RichFaces 3.1.6 version. This version works fine (when deployed on Tomcat 6).

> REGRESSION: suggestionBox in RichFaces 3.3.1 no longer works in facets (did 
> in 3.1.6)
> -------------------------------------------------------------------------------------
>
>                 Key: RF-7700
>                 URL: https://jira.jboss.org/jira/browse/RF-7700
>             Project: RichFaces
>          Issue Type: Bug
>          Components: component-input
>    Affects Versions: 3.3.1
>            Reporter: Richard Kennard
>         Attachments: suggestion31.zip
>
>
> In RichFaces 3.3.1, the <rich:suggestionBox> feature does not seem to work 
> when placed in a table facet. It works fine in RichFaces 3.1.6 (the old JSF 
> 1.1 release).
> I attach a ZIP that demonstrates the problem. The ZIP contains two Eclipse 
> projects that are identical except one (/suggestion33) uses RichFaces 3.3.1 
> and the other (/suggestion31) uses RichFaces 3.1.6.
> Both projects build to a WAR that has a single page. Hit the page 
> http://localhost:8080/suggestion31/index.jsf and you will see two 
> suggestionBoxes - one outside a table and one inside a table facet. If you 
> type in either box the suggestion pops up fine. Now hit 
> http://localhost:8080/suggestion33/index.jsf and see the same page. This 
> time,  however, the suggestionBox outside the table works but the one inside 
> the table facet never pops up.

-- 
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

        
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues

Reply via email to