flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Mclean (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-34081) Setting the text of a spark TextArea cause a script timeout error
Date Sun, 02 Mar 2014 23:47:21 GMT

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

Justin Mclean commented on FLEX-34081:

It's likely this has been fixed in 4.12 can you try the nightly build and see if that is the

> Setting the text of a spark TextArea cause a script timeout error
> -----------------------------------------------------------------
>                 Key: FLEX-34081
>                 URL: https://issues.apache.org/jira/browse/FLEX-34081
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: TextArea
>    Affects Versions: Apache Flex 4.11.0
>         Environment: Windows. Firefox, IE, Chrome, FP 11.9, FP 12
>            Reporter: Alexander Scheibe
>         Attachments: FontCrash.fxp
> Steps to reproduce: compile the attached FXP project
> Description: 
> The test application contains a text area of a specific width and height and a font size
of 14. The application also contains three embedded fonts: Myriad Pro, Rosario, Source Sans
Pro and two buttons to set a 'critical' string.
> Using the first button to set the 'critical' string of 85 characters length, the application
will become unresponsive  and will end with error #1502 "A script has executed for longer
than the default timeout period of 15 seconds." In most cases the stack trace shown in the
debug player shows that work is going on in the StandardFlowComposer, but since this is a
timeout error it may stop anywhere.
> When using the second button only the first 84 characters of the 'critical' string are
set which does not cause the error for the fonts Myriad Pro and Source Sans Pro. Also one
can see that 84 characters do not create a scroll bar. Moreover it is possible to type in
the 85 character 'f' without problems and the text area will show the vertical scroll bar.

> Additionally setting the text programmatically when the text area already shows a scroll
bar does no cause the error either. 
> So for me it looks like certain font dimensions can cause the TLF to loop in circles
when it comes to point to where a text area will show a scroll bar

This message was sent by Atlassian JIRA

View raw message