It made logical sense to me since an out of range cell reference is not editable. I know they liked range errors at Adobe, but do we want to keep this behavior ATM? If so I'll revert the change.
-Mark On Wed, Sep 4, 2013 at 8:54 PM, Justin Mclean (JIRA) <j...@apache.org>wrote: > > [ > https://issues.apache.org/jira/browse/FLEX-33710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13758595#comment-13758595] > > Justin Mclean commented on FLEX-33710: > -------------------------------------- > > Probably not the way to fix this - see: > > > http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/collections/IList.html#getItemAt() > > A range error should be thrown. > > > spark DataGrid isCellEditable is missing index bounds check > > ----------------------------------------------------------- > > > > Key: FLEX-33710 > > URL: https://issues.apache.org/jira/browse/FLEX-33710 > > Project: Apache Flex > > Issue Type: Bug > > Components: Spark: DataGrid > > Affects Versions: Apache Flex 4.10.0 > > Reporter: Mark Kessler > > Assignee: Mark Kessler > > > > The isCellEditable is not checking it's bounds for both row and column > indexes before trying to access the dataProvider and GridColumn reference. > > -- > 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 >
