flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Scheibe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLEX-34081) Setting the text of a spark TextArea cause a script timeout error
Date Mon, 03 Mar 2014 09:01:40 GMT

     [ https://issues.apache.org/jira/browse/FLEX-34081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexander Scheibe updated FLEX-34081:
-------------------------------------

    Attachment: RichEditableText.as

No 4.12 nightly does not fix this issue.

To workaround this issue I implemented a fix in RichEditableText. textContainerManager_compositionCompleteHandler
in our own SDK copy. 
I think it’s pretty heavy loop detection code. The problem I observed was that width values
alternate between the width with and without the vertical scrollbar. The code than stops the
loop at the smaller width so that the scroll bar will appear.  The same code should also work
for alternating height values. 

I attached the source of our modifications to RichEditableText, changes are tagged with @FrameworkChange.




> 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, RichEditableText.as
>
>
> 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
(v6.2#6252)

Mime
View raw message