Return-Path: X-Original-To: apmail-flex-issues-archive@minotaur.apache.org Delivered-To: apmail-flex-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 42FE310154 for ; Thu, 20 Mar 2014 10:07:49 +0000 (UTC) Received: (qmail 53871 invoked by uid 500); 20 Mar 2014 10:07:49 -0000 Delivered-To: apmail-flex-issues-archive@flex.apache.org Received: (qmail 53822 invoked by uid 500); 20 Mar 2014 10:07:47 -0000 Mailing-List: contact issues-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list issues@flex.apache.org Received: (qmail 53805 invoked by uid 99); 20 Mar 2014 10:07:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Mar 2014 10:07:46 +0000 Date: Thu, 20 Mar 2014 10:07:45 +0000 (UTC) From: "Maurice Amsellem (JIRA)" To: issues@flex.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (FLEX-34176) TextInput problem in a scaled group MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLEX-34176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941573#comment-13941573 ] Maurice Amsellem edited comment on FLEX-34176 at 3/20/14 10:06 AM: ------------------------------------------------------------------- thanks for reporting. I think the issue is in the computing of native text input font size, which takes into account application-level scale, but not parent scale. The workaround, while waiting for the fix, would be to explicitely reduce the font size in the group, when performing your scale, something like : {code} .scaleDownFont { fontSize: 6 ; /* assuming normal font-size is 12 for that resolution */ } {code} Note: if your application uses applicationDPI, you can set directly the font-size, if not, then you will have to use @media queries for defining .scaleDownFont at each applicationDPI... was (Author: mamsellem): thanks for reporting. I think the issue is in the computing of native text input font size, which takes into account application-level scale, but not parent scale. The workaround, while waiting for the fix, would be to explicitely reduce the font size in the group, when performing your scale, something like (assuming the font : {code} .scaleDownFont { fontSize: 6 ; /* half the usual value for that resolution */ } {code} Note: if your application uses applicationDPI, you can set directly the font-size, if not, then you will have to use @media queries for defining .scaleDownFont at each applicationDPI... > TextInput problem in a scaled group > ----------------------------------- > > Key: FLEX-34176 > URL: https://issues.apache.org/jira/browse/FLEX-34176 > Project: Apache Flex > Issue Type: Bug > Components: Spark: TextInput > Affects Versions: Apache Flex 4.12.0 > Environment: Mobile > Reporter: Ori Segal > Assignee: Maurice Amsellem > Priority: Critical > > While using version 4.12 mobile we encountered two issues related to TextInput component when it is included in a scaled Group - > > 1. The text is not scaled and appears cut in side the TextInput. > xmlns:s="library://ns.adobe.com/flex/spark" applicationDPI="160"> > > > > > > > > > Here is a video that shows the issue: > http://screencast.com/t/gyAnB6iDl0Gg > > 2. When the scaled Group is set with layoutDirection "rtl" the internal components disappear. > > > xmlns:s="library://ns.adobe.com/flex/spark" applicationDPI="160"> > > > > > > > > > it happens also when scaling the entire application without using applicationDPI. > The use case is mainly for low-resolution Android devices where we need to scale only an area that includes a form (otherwise the keyboard covers it) and not the rest of the application. -- This message was sent by Atlassian JIRA (v6.2#6252)