Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
Adobe Flex SDK 4.1 (Release)
-
None
-
None
-
Affected OS(s): All OS Platforms
Affected OS(s): All OS Platforms
Language Found: English
Description
Steps to reproduce:
1. Use ChangeWatcher.canWatch( myObject, 'propA.propB.propC' );
Actual Results:
Does not actually verify the bindability of the passed property chain
Expected Results:
Correctly inspect each element in the chain (the way ChangeWatcher.watch() and BindingUtils.bindProperty/Setter work)
Workaround (if any):
Manually recurse through the properties, call describeType(), and process the results. Basically, duplicating all of the logic used by the BindingUtils to attempt to set up the actual binding(s).
Note that there was a corresponding issue about the incorrect documentation for canWatch() at https://bugs.adobe.com/jira/browse/FLEXDOCS-1324, which says it was resolved (though I don't see the changes in the SDK API docs). However, "fixing" this by changing the docs is the wrong approach. We need a way to determine bindability of a property chain that doesn't involve manual duplication of the logic already in the BindingUtils. So the real "fix" for this should be making canWatch() work correctly, not modifying the docs.