[ 
https://jira.jboss.org/jira/browse/RF-5174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12440620#action_12440620
 ] 

Alex Tserbo commented on RF-5174:
---------------------------------

Actually, it was a remark with "Important" sign in the <rich:modalPanel> 
chapter:

Important:
In order to avoid a bug in IE, the root node of the dialog is moved on the top 
of a DOM tree. However, you should have a separate form inside the modal panel 
if you want to perform submits from this panel (so, no form should be around 
the modal panel in this case).

but in view of the current task it was rewritten and separated into two parts. 
Became:

Important:
To work properly, the <rich:modalPanel> should always be placed outside the 
original <h:form> and have its own <h:form> for such cases like performing 
submissions from within the <rich:modalPanel>.
 
and

Note:
In order to avoid a bug in IE, the root node of the dialog is moved on the top 
of a DOM tree.



> modalPanel definition 
> ----------------------
>
>                 Key: RF-5174
>                 URL: https://jira.jboss.org/jira/browse/RF-5174
>             Project: RichFaces
>          Issue Type: Task
>          Components: doc
>    Affects Versions: 3.2.2
>            Reporter: Svetlana mukhina
>            Assignee: Alex Tserbo
>             Fix For: 3.3.0
>
>
> Add a note in the corresponding component description section - 
> "rich:modalPanel should have its own form inside and be placed outside any 
> external ones."
> see http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146381  for 
> details 

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