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

Mark Kessler resolved FLEX-33832.
---------------------------------

       Resolution: Duplicate
    Fix Version/s:     (was: Adobe Flex SDK 4.6 (Release))
                   Apache Flex 4.11.0

> spark DataGrid editors do not work for cells that must be scrolled to
> ---------------------------------------------------------------------
>
>                 Key: FLEX-33832
>                 URL: https://issues.apache.org/jira/browse/FLEX-33832
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: DataGrid
>    Affects Versions: Apache Flex 4.10.0
>         Environment: Windows 7, Mac OS 10.8.5
>            Reporter: Michael O'Keefe
>            Assignee: Mark Kessler
>              Labels: DataGrid, Editable, Grid, GridItemEditor
>             Fix For: Apache Flex 4.11.0
>
>         Attachments: SimpleCellEditor.mxml
>
>
> Expected behavior:
> When editing a spark datagrid with editable cells that has a scrollbar due to 
> cells being out of view, I expect to be able to click on any cell to have a 
> text edit window (or custom editor) display. The edit item should stay with 
> the cell if the user scrolls the datagrid while the edit item is active.
> Actual behavior:
> When clicking to edit any cell on a scrollable grid, all cells within the 
> initial view (that is, without requiring you to scroll down) can be clicked 
> to edit as normal. However, by scrolling a little bit down, edit windows 
> begin to display several cells BELOW the clicked cell. If one scrolls further 
> and clicks on the cell, no edit window appears anywhere giving the impression 
> that the cell is not responding to edits. Furthermore, with any cell, if you 
> successfully start and item editor, if the user scrolls the grid, the item 
> editor stays stationary while the grid of cells scrolls under it. I would 
> have expected the item editor to scroll with the cell it is attached to...



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to