>I think mozilla's custom properties is more on the right track.  IOW, what is 
>it about the screen that is or isn't changing?
>Whatever it is, while it got introduced in IOS 7, it doesn't mean that 
>whatever it is won't be implemented in other OS's over time, or that there 
>will someday be an option to turn that thing on and off.  So if it is a status 
>>bar appearing, maybe the property should simply be called pop-up-status-bar, 
>or maybe the code should be watching for changes to screen-height or something 
>like that.

I see what you mean. Mozilla has other props like that:
" -moz-scrollbar-thumb-proportional"

So it could be implemented as :
"-flex-status-bar-overlap"
And maybe:
"-ios-theme"=ios7|classic

But technically, there is no way of knowing that the status bar is overlapping, 
based on "os-independent"screen change). 
The only valid test at the moment is the following:
- OS=iOS and version >= 7 + other iOS specific settings in air descriptor file.

Same for ios-theme => the internal test is based on the os+version.

 Another point is that this same "os-version" prop was meant to be used for 
seting different skins for different versions of Androids ( suggestion from Om)
Here again, we could have defined android-specific props such as:
"-flex-android-theme=A|B|C"

WDYT?

Maurice 

-----Message d'origine-----
De : Alex Harui [mailto:aha...@adobe.com] 
Envoyé : lundi 2 décembre 2013 20:05
À : dev@flex.apache.org
Objet : Re: IOS7 status bar management ( FLEX-33860)



On 12/2/13 12:34 AM, "Maurice Amsellem" <maurice.amsel...@systar.com>
wrote:
>Anyway, I think it's too late to change that:
>- changing the existing css selectors (eg. os-platform => 
>-flex-os-platform,  or application-dpi to resolution)  would break 
>existing applications
>- implementing standard W3C media css selectors will be difficult to 
>implement, and may conflict with other Flex  "responsive-design"
>techniques (states)
Yeah, I'm not suggesting going back and making it all compliant, but I am 
suggesting that we think through whether this code-path switch should really be 
tied to an OS and its version or something more "media"-oriented.  I think 
mozilla's custom properties is more on the right track.  IOW, what is it about 
the screen that is or isn't changing?
Whatever it is, while it got introduced in IOS 7, it doesn't mean that whatever 
it is won't be implemented in other OS's over time, or that there will someday 
be an option to turn that thing on and off.  So if it is a status bar 
appearing, maybe the property should simply be called pop-up-status-bar, or 
maybe the code should be watching for changes to screen-height or something 
like that.

-Alex

Reply via email to