Portlet Drag and Drop

Wed May 7 13:56:28 UTC 2008

Thanks Anastasia. Please let me know when it is fixed and I will tell the
AT vendor to try it again.

Are their other Fluid components we should be testing? I recall there was
an upload facility. Is that ready?

Also, I would like to use this as an ARIA test example for candidate
recommendation. Are there any issues?

Rich,

Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Chair, IBM Accessibility Architecture Review  Board
blog: http://www.ibm.com/developerworks/blogs/page/schwer

             Anastasia                                                     
             Cheetham                                                      
             <a.cheetham at utoro                                          To 
             nto.ca>                   Richard                             
                                       Schwerdtfeger/Austin/IBM at IBMUS      
             05/07/2008 08:07                                           cc 
             AM                        "Michelle D'Souza"                  
                                       <michelle.dsouza at utoronto.ca>,      
                                       fluid-work                          
                                       <fluid-work at fluidproject.org>       
                                                                   Subject 
                                       Re: Portlet Drag and Drop           

On 6-May-08, at 5:47 PM, Richard Schwerdtfeger wrote:

> I would like to request that the code for lightbox be modified.
> Currently, all the drop targets are marked as move when no object
> has been selected for drag. Dropeffect should be set to none until a
> drag operation has been selected. Once an object has been grabbed
> you should then set the dropeffects on the appropriate targets to
> "move." After drag has been stopped all dropeffects should be set
> back to none.
>
> Reasoning:
>            • You don't know if you can drop the source on the target. You
will
> have other widgets in a portal application and if you grab them for
> dragging you are saying that they can be dropped on the gridcells.
> So, dropeffect should be set to "none" until a drag has started and
> you know what operation can be performed on the target.
>            • The AT is looking for objects which can receive an object
that
> has been grabbed. Pre-marking targets before an object is selected
> for drag is confusing.
>

Rich, thanks for this email. It's really great to have your expertise
helping us to understand the ARIA states and properties, and apply
them correctly. It seems in this case, we are not using the dropeffect
properly - we'll definitely fix that.

--
Anastasia Cheetham                   a.cheetham at utoronto.ca
Software Designer, Fluid Project    http://fluidproject.org
Adaptive Technology Resource Centre / University of Toronto

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20080507/742df856/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20080507/742df856/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic14707.gif
Type: image/gif
Size: 1255 bytes
Desc: not available
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20080507/742df856/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20080507/742df856/attachment-0002.gif>