[ 
https://issues.apache.org/jira/browse/JS2-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Sean Taylor reassigned JS2-752:
-------------------------------------

    Assignee: Steve Milek

> Desktop pipeline: drag and drop and portlet relocation
> ------------------------------------------------------
>
>                 Key: JS2-752
>                 URL: https://issues.apache.org/jira/browse/JS2-752
>             Project: Jetspeed 2
>          Issue Type: Bug
>    Affects Versions: 2.1.2
>         Environment: Tomcat 5.5, IE 6 and FF2.0.0.4
>            Reporter: Yang Sie
>            Assignee: Steve Milek
>             Fix For: 2.1.3, 2.2
>
>
> This was NOT an issue in June 28 2007 code drop. Now it is broken. Simply 
> put, the problem is that larger portlet (height wise) does not  automatically 
> moves up to fill the void. Details as following...
> On default page (Welcome to Jetspeed 2), it is a two column layout, full of 
> small (S: height is small) or large (L: height is large) portlets in two 
> columns, as below:
>  
> column 0      column 1
> -----------------------------------
> portletA (S) | portletD (S)
> portletB (S) | portletE (L)
> portletC (L) | 
>  
> now you drag portletA to move it to column 1, portletB moves up to take 
> portletA's position (while portletC stayed where it was). At this time, you 
> can move portlet A back to its original position or the empty area where 
> portletB was. However, in my understanding, after portletA is moved out, 
> besides portletB moves up, portletC should also be moving up automatically to 
> take over the old portletB position. it didn't happen. ALSO, you can't even 
> manually drag portletC up to old portletB location.   As matter of fact, 
> yesterday, with JS2.1.2 code base, even portletB didn't move up (therefore, 
> old portletA position was a white space, today with the patch that fixed the 
> NoActions Layout issue corrected the moving problem partially, at least 
> portletB now moves up automatically, but portlet B doesn't). This feature was 
> always working and was still working in my June 28 code drop.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to