Spreading Funkyness

Recently I stumbled upon a curious issue. Can’t tell whether it is a bug or a feature. For sure it is something unexpected to me. I stripped it down to a minimal example.

Create an empty Adobe Air application and link a css stylesheet.

1
2
3
4
5
6
7

<?xml version="1.0" encoding="utf-8"?>
<mx:WindowedApplication 
        xmlns:mx="http://www.adobe.com/2006/mxml" 
        layout="vertical"
        >
	<mx:Style source="style.css"/>
</mx:WindowedApplication>

The CSS only sets the background color like this:

1
2
3

WindowedApplication {
   backgroundColor: #000000;
}

In the application descriptor set the chrome to none like this:

1

<systemChrome>none</systemChrome>

If you run the application you’ll get the following result.

So far everything is behaving like expected. We have a window, with a black background, no system chrome and the flex chrome is visible.

Let’s try to modify the mxml and set the showFlexChrome to false like the following:

1
2
3
4
5
6
7
8

<?xml version="1.0" encoding="utf-8"?>
<mx:WindowedApplication 
        xmlns:mx="http://www.adobe.com/2006/mxml" 
        layout="vertical" 
        showFlexChrome="false"
        >
	<mx:Style source="style.css"/>
</mx:WindowedApplication>

You would expect to see a black rectangle, with no flex chrome, but instead there is a rectangle with
the default flex color. Why?

If you want to play with the example here is the source code.

Similar Posts

• No drop shadow when systemChrome is none
• Dynamic function calling in Flex
• Passing parameters to Adobe Air at startup