Is the HALO app using the new namespace or is it using the old one and/or
Our Halo application uses a CSS file which uses the new namespaces
@namespace s "library://ns.adobe.com/flex/spark";
But the Halo components still use the old namespace definitions like <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml", is that a problem?
Only the Spark only modules are using:
Something else also weird is if I load our module in a dummy spark app, any external swc that uses defaults.css, is preserved but in our main halo app, I have to redefine again everything that was in that defaults.css.
I'm not sure whether CSS namespaces are tied to the app namespace, but they
You might also try using custom skins for non-popups and see if that works.
I think there is some bug, don't know where but it could be at the compiler level? If I have everything spark only and have a structure like this
- custom components libs with corresponding defaults CSS
- spark only module with a defaults CSS
- spark application using using module in point 2)
this doesn't require me to define anything in style.css for application in 3). Everything is inherited as expected, custom components in 1) used in 2) are properly renderer in 3).
In our main app we have 1) and 2) unchanged but 3) is a Halo app (only mx components) and everything on defaults.css in 1) and in 2) must be defined in the main app otherwise it won't work. Should I log a bug for this?