[ 
https://issues.apache.org/jira/browse/FLEX-33994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940336#comment-13940336
 ] 

Maurice Amsellem edited comment on FLEX-33994 at 3/19/14 2:14 PM:
------------------------------------------------------------------

Will implement the following @media selectors:
device-width, device-height

and the following units:
(no unit), px, pt, in, cm, dp 
no unit => physical pixels
px => physical pixel
pt => pixels-equivalent at 72 ppi 
dp => pixels-equivalent at 160 ppi (use bucket dpi)

[Edit]
Note: pt, in and cm uses the real device dpi
while dp will use the bucket-dpi (normalized dpi)




was (Author: mamsellem):
Will implement the following @media selectors:
device-width, device-height

and the following units:
(no unit), px, pt, in, cm, dp 
no unit => physical pixels
px => physical pixel
pt => pixels-equivalent at 72 ppi 
dp => pixels-equivalent at 160 ppi (use bucket dpi)

[Edit]
Note: pt, in and cm uses the real device dpi
while dp will use the bucket-dpi (normalized dpi)
Not sure if I should use the original device resolution (ie 132dpi for iPad) or 
the normalized resolution (ie 120,160,etc.) for the conversion of units to 
actual pixels (which is required for comparison).



> Need a way to distinguish phone and tablet target devices through css
> ---------------------------------------------------------------------
>
>                 Key: FLEX-33994
>                 URL: https://issues.apache.org/jira/browse/FLEX-33994
>             Project: Apache Flex
>          Issue Type: New Feature
>          Components: .Unspecified - Mobile
>    Affects Versions: Apache Flex 4.11.0
>            Reporter: Maurice Amsellem
>            Assignee: Maurice Amsellem
>
> Some components should have different layout on phone and tablet devices.
> For example, DropDownList should display as a centered popup list on phones, 
> and display the drop down list below its popup button on tablets, supposedly 
> having move screen space.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to