>FlexJS has some non-standard styles for injecting beads so we need an >equivalent MQ parser in AS.
Yes, I remember that in your presentation. Beads can also be configured in defaults.css, like skinClass. But the rest of the css could be pushed to the browser, so it needs to be compliant. >That said, while there's lots of Flex that isn't CSS compliant, whenever we >add more non-compliance it implies adding another migration task for folks >>migrating projects to FlexJS because FlexJS will likely be more compliant >since it wants to rely on the underlying browser CSS as much as possible. I will keep that in mind. >Anyway, do what you think is right. I don't have any particular objection to >any of your plans, I just wanted make sure you thought about how FlexJS >might >present similar capabilities. Ok. Thanks for your help. Maurice -----Message d'origine----- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mercredi 19 mars 2014 17:46 À : dev@flex.apache.org Objet : Re: Advice needed on FLEX-33994 On 3/19/14 8:52 AM, "Maurice Amsellem" <maurice.amsel...@systar.com> wrote: >>What do folks do in the HTML/JS/CSS world? >From what I read on the web, they use media queries, with a combination >of width/height ( type=handheld is not used, as it's not well supported). > >For Flex JS, you could rely entirely on the browser's media query >parser, so that would be easy. right ? FlexJS has some non-standard styles for injecting beads so we need an equivalent MQ parser in AS. But sure, there's no obligation to do the same thing for the current SDK if it doesn't make sense. That said, while there's lots of Flex that isn't CSS compliant, whenever we add more non-compliance it implies adding another migration task for folks migrating projects to FlexJS because FlexJS will likely be more compliant since it wants to rely on the underlying browser CSS as much as possible. -Alex
