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

Brian Leathem updated RF-12735:
-------------------------------

    Fix Version/s: 5-Tracking

    
> Metamer: DnD: rich:dragSource: dropping causes Error status [myfaces]
> ---------------------------------------------------------------------
>
>                 Key: RF-12735
>                 URL: https://issues.jboss.org/browse/RF-12735
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-drag/drop
>    Affects Versions: 4.3.0.CR1
>         Environment:     RichFaces 4.3.0.CR1
>     Metamer 4.3.0.20130114-CR1
>     Weld Servlet (Uber Jar) 20120106-1159
>     Apache Tomcat 7.0.32
>     Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
>     Firefox 17.0 @ Linux i686 (browser doesn't influence it)
> Metamer:
> 2023898d4b163a889955c1d028149a31  
> metamer-4.3.0.20130114-CR1-tomcat7-myfaces.war
>            Reporter: Ján Jamrich
>             Fix For: 5-Tracking
>
>
> Dropping doesn't work for componsite component example (even simple example 
> for dragSource works correctly).
> When drag from first draggable area and drop in first dropping area 
> (indicator indicated Accepting), object is not "accepted" - doesn't appears 
> in dropping area, and error status appears in Metamer header.
> When change type to drg2 then still doesn't for first dropping area. Only 
> second droppiing area works correctly, even drg2 should be accepted by both 
> dropping areas (and dragIndicator is indicating accepting over dropping1 area)
> Indicator type doesn't influence behavior.

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

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

Reply via email to