History | Log In     View a printable version of the current page.  
Issue Details (XML)

Key: SDK-11718
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: C C
Assignee: Joan Lafferty
Reporter: Joan Lafferty
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Flex SDK

Setting the style 'color' on a DateField does not affect all the text in the DateChooser popup

Created: 07/11/07 06:36 PM   Updated: 04/01/08 06:46 PM
Component/s: mx: DateField
Security Level: Public (All JIRA Users )

File Attachments: 1. File colorBug.mxml (0.3 kb)
2. File colorBug.swf (191 kb)

Issue Links:
Relationship
 
This issue is related to by:
SDK-12155 Style set like a property in DateFiel... C Closed
SDK-15138 Using multiple selectors for dateChoo... None Internal Review

Severity: Incorrectly Functioning
Reproducibility: Every Time
Discoverability: Medium
Found in Version: SDK Moxie M3 (Beta 2)
Milestone: SDK Moxie (Feature Complete)
Affected OS(s): All OS Platforms
Steps to Reproduce:
Steps to reproduce:
1. Load the bugfile.
2. Open the first DateField DateChooser. The color style is set in the dateChooserStyleName.
3. Open the second DateField DateChooser. The color style is set on the DateField.
 
 Actual Results: The month days are not the correct color in the DateChooser popup where 'color' was set on the DateField.
 
 
 Expected Results: The month days should be a bluish color.
 
 
 Workaround (if any):
 
 
 
Language Found: English
Bugbase Id: none
Triaged: No
Regression: Yes
QA Owner: Joann Chuang
Resolved by: Jason Szeto
Confirmed Version: SDK Moxie M3 (Beta 2) - 176702
Participants: Jason Szeto and Joan Lafferty


 All   Comments      Sort Order:
Joan Lafferty - [07/11/07 06:37 PM ]
Opening to Jason since this has to do with the style changes to PopUpManager, DateField and DateChooser made for Moxie.

Jason Szeto - [07/12/07 08:09 PM ]
The CalendarLayout type selector's definition for the color style was taking precedence over the inherited style from the DateField. This is the expected behavior for inherited styles. However, for the DateField, we want to make it seem more like a unified component.

The solution is to assign a StyleProxy with no filters to the styleName of the DateField dropdown. This means no nonInheriting styles will get passed through, but that inheriting styles will be calculated in a different order, giving precedence to the override in the DateField. In order to get the dateChooserStyleName class selector onto the DateChooser, I had to reimplement the hack of putting the class selector onto the styleDeclaration of the DateChooser. Not ideal, but necessary to resolve this issue.

The StyleProxy filters are not exposed because we don't want any nonInheriting styles to be passed from the DateField to the DateChooser. That's what the dateChooserStyleName style is for.

Joan Lafferty - [07/16/07 12:42 PM ]
confirmed fixed in build 176668. Closing bug.