Click here to crash your browser
April 1st, 2008 . by polygeekWhile writing the code for the previous post I ran into a problem: my browser kept crashing when I’d publish my Flex project. All that was happening was that a <mx:Button> and <mx:TextArea> were fading in-and-out using <mx:Fade>.
| view source |
Sure enough, it would cycle through about 4 times and start getting all jittery and then kaboom! Down goes the browser.
All that’s happening, in this example, is that when you click the top button it starts the other two buttons sliding back and forth. When one <mx:Move> is complete it calls an onTweenLeftEnd which starts the tween to the right. Back and forth we go.
If instead you use <mx:Fade> to fade the buttons in-and-out you get the same result. This doesn’t happen if you move or fade just one <mx:Button>. And it seems to happen with any two UIComponents.
Solution here.
I’ll do a more lengthy post on the problem you coming across (basically the overhead of MXML), but I’ve tried posting it here 3 times now and each time your blog wouldn’t accept it.
I am also posting from FF as your blog recognizes me in Safari. I does give me an anti-spam word cos it recognizes me, but when u post it errors stating I didn’t enter the anti-spam word, which I WASN’T given.
@Tink, nice work on the solution. And it’s more elegant as well. No surprise there.
Sorry about the trouble commenting. I thought I had all my comment-spam plugins disabled but there was one I missed. Hopefully it won’t be a problem in the future.
Yes, comments now work, thanks ;)
Leave a Reply