|
If you were logged in you would be able to see more operations.
|
|
|
Flex SDK
Created: 09/18/07 05:24 PM
Updated: 10/16/07 03:34 PM
|
|
| Component/s: |
mx: List
|
|
Security Level:
|
Public
(All JIRA Users
)
|
|
| Severity: |
Usability Issue
|
| Reproducibility: |
Every Time
|
| Discoverability: |
Medium
|
| Found in Version: |
SDK Moxie M3 (Beta 2)
- 182682
|
| Milestone: |
|
| Affected OS(s): |
All OS Platforms
- All
|
| Steps to Reproduce: |
dataChangeEffect on ListBase is declared as a Style, not as an Effect. This is confusing and causes bug FLEXDOCS-134. Also, the name makes it sound like it is triggered by ListBase's dataChange event, which is not the case.
After a discussion between Mike, Glenn, Ely, Jason, and Gordon, the recommendation is that this should be replaced with
[Effect(name="itemsChangeEffect", event="itemsChange")]
Note that itemsChange is a non-existent event; several chart effects use fake triggers.
dataChangeEffect on ListBase is declared as a Style, not as an Effect. This is confusing and causes bug FLEXDOCS-134. Also, the name makes it sound like it is triggered by ListBase's dataChange event, which is not the case.
After a discussion between Mike, Glenn, Ely, Jason, and Gordon, the recommendation is that this should be replaced with
[Effect(name="itemsChangeEffect", event="itemsChange")]
Note that itemsChange is a non-existent event; several chart effects use fake triggers.
|
| Language Found: |
English
|
| Bugbase Id: |
none
|
| Triaged: |
Yes
|
| Regression: |
No
|
| QA Owner: |
Ella Mitelman
|
| Resolved by: |
Ryan Frishberg
|
| Participants: |
Ella Mitelman, Gordon Smith, Lauren Park and Ryan Frishberg
|
|
All
|
Comments
|
|
Sort Order:
|
|
Bug
Closed
C
dataChangeEffect is declared as a Style, not an Effect, and is not triggered by the dataChange event