Well there has to be an order of override: If there is a conflict the inline declared style property wins over something buried inside a style attribute, but I am not a code usability expert :) Also I am hopeful that tooling would mature eventually but I would avoid counting on it if I can.
You have to remember that components in new flex framework would be composite as well & they would have underlying components that would need to have their styles exposed as well Talk is cheap so I will pull some code sample & I guess we can more effectively arbitrate on that. Thanks, Pratyoosh -----Original Message----- From: Alex Harui [mailto:aha...@adobe.com] Sent: Wednesday, September 04, 2013 12:17 PM To: dev@flex.apache.org Subject: Re: [FlexJS] General questions On 9/4/13 9:04 AM, "Cosma Colanicchia" <cosma...@gmail.com> wrote: >2013/9/4 Alex Harui <aha...@adobe.com> > >> Maybe we'll have an 'customStyles' object for styles that aren't in >> CSS > > >+1 (I would prefer simply "styles" as for the name) Maybe, but then folks might stuff all of their styles in there. Which would work, but maybe we shouldn't invite them to do that? What wins if you do: <foo style="color:red" color="red" /> -Alex This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.
