[svn:fx-trunk] 12865: Fix mx.controls.HTML and mx.core. FlexHTMLLoader so the participate in the current IME scheme

Revision: 12865
Revision: 12865
Author:   [email protected]
Date:     2009-12-11 13:51:27 -0800 (Fri, 11 Dec 2009)
Log Message:
Fix mx.controls.HTML and mx.core.FlexHTMLLoader so the participate in the current IME scheme
QE Notes: None
Doc Notes: None
Bugs: SDK-24391
Reviewer: Corey
API Change: No
Is noteworthy for integration: No
tests: checkintests mustella/apollo/HTML
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24391
Modified Paths:
    flex/sdk/trunk/frameworks/projects/airframework/src/mx/controls/HTML.as
    flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/FlexHTMLLoader.as

OK, Just changed the screen option in DEVICE... And now I'm getting this in my log files. When I try and install that package with pacman, it wants to remove the normal nvidia driver. Can I run one for each graphics card?
Xorg.0.log
(II) Module "ramdac" already built-in
(WW) NVIDIA(0): The NVIDIA GeForce FX 5200 GPU installed in this system is
(WW) NVIDIA(0): supported through the NVIDIA 173.14.xx Legacy drivers.
(WW) NVIDIA(0): Please visit http://www.nvidia.com/object/unix.html for
(WW) NVIDIA(0): more information. The 185.18.36 NVIDIA driver will ignore
(WW) NVIDIA(0): this GPU. Continuing probe...
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888

Similar Messages

[svn:fx-trunk] 13136: Fix for FLEXENT-1196 ( Replay of click on NavigatorContent does not close the combobox)

Revision: 13136
Revision: 13136
Author:   [email protected]
Date:     2009-12-21 17:40:28 -0800 (Mon, 21 Dec 2009)
Log Message:
Fix for FLEXENT-1196 (Replay of click on NavigatorContent does not close the combobox)
We need not record OPEN event when it is triggered from a KeyBoard event that types a character. Replaying the type event would automatically open the drop down.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FLEXENT-1196
Modified Paths:
    flex/sdk/trunk/frameworks/projects/automation_spark/src/spark/automation/delegates/compon ents/SparkComboBoxAutomationImpl.as
    flex/sdk/trunk/frameworks/projects/automation_spark/src/spark/automation/delegates/compon ents/supportClasses/SparkDropDownListBaseAutomationImpl.as

[svn:fx-trunk] 12295: fix for FLEXDOCS-889, and add doc on the WindowedApplication.useNativeDragManager property

Revision: 12295
Revision: 12295
Author:   [email protected]
Date:     2009-11-30 13:41:29 -0800 (Mon, 30 Nov 2009)
Log Message:
fix for FLEXDOCS-889, and add doc on the WindowedApplication.useNativeDragManager property
QE notes: -
Doc notes: -
Bugs: - FLEXDOCS-889
Reviewer: -
Tests run: - checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/FLEXDOCS-889
    http://bugs.adobe.com/jira/browse/FLEXDOCS-889
Modified Paths:
    flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/WindowedApplication.as
    flex/sdk/trunk/frameworks/projects/airspark/src/spark/components/WindowedApplication.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/styles/metadata/AnchorStyles.as

[svn:fx-trunk] 5114: Fix FxRadioButton doc bug and fix the bug fix I messed up yesterday.

Revision: 5114
Author: [email protected]
Date: 2009-02-27 12:50:47 -0800 (Fri, 27 Feb 2009)
Log Message:
Fix FxRadioButton doc bug and fix the bug fix I messed up yesterday.
QE Notes: mustella gumbo/RadioButtons passed
Doc Notes:
Bugs: SDK-19475, SDK-19531
Reviewers:
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19475
http://bugs.adobe.com/jira/browse/SDK-19531
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/FxRadioButton.as

[svn:fx-trunk] 7868: Fixed bug in flex4test testWheel app; it needed to be updated to the latest effects API after motionPaths changed from an Array to a Vector . MotionPath

Revision: 7868
Author:   [email protected]
Date:     2009-06-15 16:37:33 -0700 (Mon, 15 Jun 2009)
Log Message:
Fixed bug in flex4test testWheel app; it needed to be updated to the latest effects API after motionPaths changed from an Array to a Vector.
Modified Paths:
    flex/sdk/trunk/development/eclipse/flex/flex4test/src/testWheel.mxml

Walter Laan wrote:
almightywiz wrote:
Walter Laan wrote:
The security popup really messes with the focus in Firefox (3.6.16) though.Not saying you're wrong, but I'm using FireFox 3.6.16, as well, and I have none of the focus troubles you've described.Cannot reproduce it now either. Weird.I got the impression you were referring to keyboard focus, so I did some further tests on focus behavior. The test results are listed in the Accumulated Results table on the 1st post.
The only browser so far that works as I'd expect, or at least as I'd like, is IE.
Applets and keyboard navigation have always been a PITA. Some time ago I vaguely recall seeing an update involving a new parameter to regulate initial focus (applet or page, ..or another applet), but for the life of me I cannot locate it now. Given that it was a parameter for initial focus, I doubt it would help in this case.
Edited by: Andrew Thompson on Mar 26, 2011 6:18 PM
Removed table which has now been expanded & added to 1st post.

[svn:fx-trunk] 10866: Fix broken links in ASDoc comments for TLFTextInput. as and TextArea.as, and add OverrideBase.as to ASDoc output

Revision: 10866
Author:   [email protected]
Date:     2009-10-05 08:56:44 -0700 (Mon, 05 Oct 2009)
Log Message:
Fix broken links in ASDoc comments for TLFTextInput.as and TextArea.as, and add OverrideBase.as to ASDoc output
QE notes: -
Doc notes: -
Bugs: -
Reviewer: -
Tests run: - checkintests
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/states/OverrideBase.as
    flex/sdk/trunk/frameworks/projects/spark/src/mx/controls/TLFTextInput.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/TextArea.as

Sorry about that. I am not exactly sure where the problem is, but I know it takes place after I put the <nav> in (in the html portion). If I understand what I am learning, the CSS at the top will structure my html code so I would have thought the CSS tageting my nav would be the focus. Maybe it is a different section though.
CSS part:
nav p {
font-size: 90%;
color: #FFC;
text-align: right;
font-weight: bold;
background-color: #090;
padding-top: 5px;
padding-right: 20px;
padding-bottom: 5px;
border-top-width: 2px;
border-top-style: solid;
border-top-color: #060;
HTML part: (bold italic is the part I added)
<body>
<div class="container">
<div id="apDiv1"><img src="Lessons/images/butterfly-ovr.png" width="170" height="158" alt="GreenStart Logo"></div>
<header></header>
<nav>
    <p>Home | About Us | Contact Us</p>
</nav>
<div class="sidebar1">
    <ul class="nav">
      <li><a href="#">Green News</a></li>
      <li><a href="#">Green Products</a></li>
      <li><a href="#">Green Events</a></li>
      <li><a href="#">Green Travel</a></li>
      <li><a href="#">Green Tips</a></li>
    </ul>

[svn:fx-trunk] 10898: Fix for a bug: After playing a hide effect, a window wouldn't be visible again.

Revision: 10898
Author:   [email protected]
Date:     2009-10-06 13:54:04 -0700 (Tue, 06 Oct 2009)
Log Message:
Fix for a bug: After playing a hide effect, a window wouldn't be visible again.
The issue here is that all effects that occur because of HIDE end up calling setVisible() (see EffectManager.effectEndHandler). Window/WindowedApplication was basically left with two concepts of setVisible...the displayObject one and the native application one, and they were out of synch. So setting visible=true on the window wasn?\226?\128?\153t calling setVisible(true) which controls the display object visibility. Now instead of doing our work in the visible setter, we override setVisible() and do it in there.
QE notes: -
Doc notes: -
Bugs: SDK-23263
Reviewer: Darrell
Tests run: checkintests, Rob ran mustella window/windowedapplication
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23263
Modified Paths:
    flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/Window.as
    flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/WindowedApplication.as
    flex/sdk/trunk/frameworks/projects/airframework/src/spark/components/Window.as
    flex/sdk/trunk/frameworks/projects/airframework/src/spark/components/WindowedApplication. as

I run Suse 9.1 Linux, and Suse has a package called lmsensors which by default on my machine gives readings like this:
Code: [Select]
temp1: +27°C (high = +0°C, hyst = +22°C) sensor = thermistor
temp2: +41.0°C (high = +80°C, hyst = +75°C) sensor = PII/Celeron diode
Now that 41C is pretty high for an idle AMD643000+ running at 1000Mhz, 1.08V. Too high, I would say. temp 1 in this case is the SYS temp, temp2 is the CPU temp.
Now, using lmsensors I can duplicate your little trick and tell it that temp 2 is in fact a 3904 transistor. Having done this can I get readings like this:
Code: [Select]
temp1: +27°C (high = +0°C, hyst = +22°C) sensor = thermistor
temp2: +16.0°C (high = +80°C, hyst = +75°C) sensor = 3904 transistor
Problem is, I'm not sure that the sensor is actually a 3904 transistor! The number's lower, but I was pretty sure that the sensor in the AMD64 is in fact a diode. Also, surely the CPU temp can't actually be that much lower than the SYS temp.
So, I think your fix succeeds in giving lower temps and that's great in that it will tell your system software that the CPU is not overheating, but I don't think it's the solution to high temp reporting. Anyway, as you say, its a solution for people who can't run with system shutdowns due to bogus high temps.
I've been looking at these temp issues with the MSI K8T, and I was thinking the problem was simply a miscalibration. The Winbond sensor chip on my board (maybe the K8N is the same, maybe not) has a sensor temp offset that gets added to the temp coming from the sensor. On the K8T this number is +54C. Funny number I know, but I've "fixed" the problem while I wait for a real bios fix on the K8T by simply reducing this offset to give me a CPU temp that matches SYS temp when idle. This enables cool'n'quiet fan control to work properly on my system, which is my main practical concern.

[svn:fx-trunk] 10960: Fixed performance of Wipe effect.

Revision: 10960
Author:   [email protected]
Date:     2009-10-09 13:55:47 -0700 (Fri, 09 Oct 2009)
Log Message:
Fixed performance of Wipe effect. It turns out that micro-tuning the shader code is very important, since that same inner loop runs on every pixel of the bitmap being affected. This change splits the single Wipe shader (with a direction parameter) into four separate Wipe shaders (WipeLeft, etc.), to avoid a switch on the direction parameter. Also, it avoids some setup of pixel values, only bothering to sample the pixel values after it determines which image to sample from. Little stuff, but gained about 20-25% performance on some sample wipe effects.
QE notes: This broke 3 Wipe effects tests because the old WipeEffectInstance class went away. These tests have supposedly been updated by the time this checkin is happening.
Doc notes: No
Bugs: sdk-23279
Reviewer: Corey
Tests run: checkintests, mustella spark/effects
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-23279
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Wipe.as
Added Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeDown.pbj
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeDown.pbk
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeLeft.pbj
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeLeft.pbk
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeRight.pbj
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeRight.pbk
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeUp.pbj
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/WipeUp.pbk
Removed Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Wipe.pbj
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/Wipe.pbk
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/WipeInstance.as

[svn:fx-trunk] 5386: * Fix for Flex Builder JUnit tests.

Revision: 5386<br />Author: [email protected]<br />Date: 2009-03-18 08:03:11 -0700 (Wed, 18 Mar 2009)<br /><br />Log Message:<br />-----------<br />* Fix for Flex Builder JUnit tests.<br /><br />tests Passed: checkintests, performance testsuite<br /><br />Needs QA: YES<br /><br />Needs DOC: NO<br /><br />API Change: NO<br /><br />Reviewer: Pete F.<br /><br />Code-level description of changes:<br /> <br /> compiler/CompilerAPI.java<br /><br /> Changed the deleted Map used in validateCompilationUnits() and<br /> some of it's helper methods from <String, Source> to <QName,<br /> Source>. This allows us to track when a definition is deleted<br /> from one SWC in the library path and then added by another SWC in<br /> the library path. All the definitions dependant on the definition<br /> need to be recompiled and we were missing this before.<br /> Specifically, the Flex Builder JUnit tests were switching from<br /> airglobal.swc to playerglobal.swc midstream. As a result, we<br /> weren't recompiling classes that depended on<br /> flash.display.DisplayObjectContainer, because it looked like it<br /> hadn't been deleted.<br /><br />Modified Paths:<br />--------------<br /> flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerAPI.java<br /> flex/sdk/trunk/modules/compiler/src/java/flex2/tools/oem/Library.java

[svn:fx-trunk] 8474: * Fixed the AST generation code path of Vector typed variables and

Revision: 8474
Author:   [email protected]
Date:     2009-07-09 07:20:32 -0700 (Thu, 09 Jul 2009)
Log Message:
Fixed the AST generation code path of Vector typed variables and
properties with Bindable.
tests Passed: checkintests
Needs QA: YES
Needs DOC: NO
Bug fixes: SDK-21587
API Change: NO
Reviewer: Peter D.
Code-level description of changes:
   AbstractSyntaxTreeUtil.java
     Modified generateParameter(*) to use generateTypeExpression().
   binding/BindableSecondPassEvaluator.java
     Modified generateGetter() to use AbstractSyntaxTreeUtil.generateTypeExpression().
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21587
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/AbstractSyntaxTreeUtil.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/BindableSecondPassEva luator.java

I got again a total system freeze today when I wanted to launch firefox using only the openbox menu, without wbar running.
So I decided to try now the 'nouveau.noaccel=1' kernel command line parameter, and to use again wbar for my frequently used applis.
In the Xorg log, the differences are:
without 'nouveau.noaccel=1'
[ 30.761] (II) UnloadModule: "nv"
[ 30.761] (II) Unloading nv
[ 30.761] (--) Depth 24 pixmap format is 32 bpp
[ 30.762] (II) NOUVEAU(0): Opened GPU channel 0
[ 30.765] (II) NOUVEAU(0): [DRI2] Setup complete
[ 30.765] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
[ 30.765] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
[ 30.776] (II) EXA(0): Driver allocated offscreen pixmaps
[ 30.777] (II) EXA(0): Driver registered support for the following operations:
[ 30.777] (II) Solid
[ 30.777] (II) Copy
[ 30.777] (II) Composite (RENDER acceleration)
[ 30.777] (II) UploadToScreen
[ 30.777] (II) DownloadFromScreen
[ 30.777] (==) NOUVEAU(0): Backing store disabled
[ 30.777] (==) NOUVEAU(0): Silken mouse enabled
with 'nouveau.noaccel=1'
[ 1191.621] (II) UnloadModule: "nv"
[ 1191.621] (II) Unloading nv
[ 1191.621] (--) Depth 24 pixmap format is 32 bpp
[ 1191.621] (EE) NOUVEAU(0): Error creating GPU channel: -19
[ 1191.621] (EE) NOUVEAU(0): Error initialising acceleration. Falling back to NoAccel
[ 1191.621] (==) NOUVEAU(0): Backing store disabled
[ 1191.621] (==) NOUVEAU(0): Silken mouse enabled
[ 1191.621] (==) NOUVEAU(0): DPMS enabled
So now 3D acceleration is disabled.
I will see now if the system is stable enough for my daily usage and gives satisfactory performances.
I am almost sure that the mesa nouveau dri driver is the cause of the freezes.
Last edited by berbae (2013-03-27 10:07:42)

[svn:fx-trunk] 10051: fix the build. xml that we include in the package in the frameworks directory.

Revision: 10051
Author:   [email protected]
Date:     2009-09-08 07:53:47 -0700 (Tue, 08 Sep 2009)
Log Message:
fix the build.xml that we include in the package in the frameworks directory.
-remove haloclassic
-add textlayout
-reorganize the targets
QE notes: no
Doc notes: no
Bugs: sdk-22441
Reviewer: n/a
Tests run: checkintests
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-22441
Modified Paths:
    flex/sdk/trunk/frameworks/build_framework.xml

[svn:bz-trunk] 20753: * Fixed non UTF8 compliant char in EndpointPushNotifier.java

Revision: 20753
Revision: 20753
Author:   [email protected]
Date:     2011-03-10 02:40:52 -0800 (Thu, 10 Mar 2011)
Log Message:
Fixed non UTF8 compliant char in EndpointPushNotifier.java
Added tomcat7 support to the maven build of blazeds opt (to support security/Tomcat7Valve.java)
tested the build with maven3
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/client/EndpointPushNotifier.java
    blazeds/trunk/modules/opt/pom.xml
    blazeds/trunk/modules/opt/poms/tomcat4/pom.xml
    blazeds/trunk/modules/opt/poms/tomcat6/pom.xml
    blazeds/trunk/modules/pom.xml
Added Paths:
    blazeds/trunk/modules/opt/poms/tomcat7/
    blazeds/trunk/modules/opt/poms/tomcat7/pom.xml
Property Changed:
    blazeds/trunk/modules/
    blazeds/trunk/modules/common/src/
    blazeds/trunk/modules/core/src/
    blazeds/trunk/modules/remoting/src/

[svn:fx-trunk] 13201: Fix RTE when calling PopUpManager.createPopUp() from a module or sub-application.

Revision: 13201
Revision: 13201
Author:   [email protected]
Date:     2009-12-23 12:16:41 -0800 (Wed, 23 Dec 2009)
Log Message:
Fix RTE when calling PopUpManager.createPopUp() from a module or sub-application.
This fix adds a moduleFactory parameter to PopUpManager.createPopUp() to allow a module or sub-application to specify the style manager to be used. Modules and sub-applications should always pass a moduleFactory to PopUpManager.createPopUp() or PopUpManager.addPopUp() to ensure the correct style manager is used when looking up styles. Otherwise the parent of the pop up is used to determine the style manager.
QE notes: Please create a PerModuleStyles test that uses the new parameter to createPopUp().
Doc notes: None.
Bugs: SDK-24835.
Reviewer: Alex
Tests run: checkintests, Managers/PopUpManager
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24835
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/IPopUpManager.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/PopUpManager.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/PopUpManagerImpl.as

[svn:fx-trunk] 12078: Fix for change events in Slider and ScrollBar.

Revision: 12078
Revision: 12078
Author:   [email protected]
Date:     2009-11-21 00:14:46 -0800 (Sat, 21 Nov 2009)
Log Message:
Fix for change events in Slider and ScrollBar. They now dispatch change events as before, whenever the user alters the value. In addition, changeStart and changeEnd events will be dispatched at the start and end of a user interaction or animation.
TrackBase.as - Added metadata for changeStart/End events. Dispatch change, changeStart/End events when appropriate.
Slider.as - Dispatch change, changeStart/End events when appropriate.
ScrollBar.as - Dispatch the appropriate events. Note that changeStart/End will not dispatch when shift-clicking on a non-animating ScrollBar. Renamed animatingSinglePage to animatingOnce to better reflect its function. Refactored some method calls to the new private stopAnimation(), which is more consistent with Slider. Refactored the button handlers to make stepping more readable. Added a setValue call in animationEndHandler where we were ending up off the snapInterval when shift-clicking.
Updated FlexEvent, ScrollBarTestScript and VideoPlayer to handle the new events.
QE notes: Update Slider and ScrollBar tests
Doc notes: No
Bugs: SDK-24264
Reviewer: Ryan
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24264
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/events/FlexEvent.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/VideoPlayer.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/ScrollBar.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/Slider.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/TrackBase.as
    flex/sdk/trunk/frameworks/tests/basicTests/spark/scripts/ScrollBarTestScript.mxml

[svn:fx-trunk] 5473: Fix for bug around handling of constraints during and after effects were run , both for old and new effects.

Revision: 5473
Author: [email protected]
Date: 2009-03-20 16:02:58 -0700 (Fri, 20 Mar 2009)
Log Message:
Fix for bug around handling of constraints during and after effects were run, both for old and new effects. Fix was to correctly record and handle styles that were set or not set in either state and to temporarily set width/height values for the duration of an effect if we disabled the relevant styles that affect width/height.
QE Notes: None
Doc Notes: None
Bugs: SDK-17809
Reviewer: Jason
Testing: checkintests, Mustella Effects, ListDataEffects
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-17809
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateInstance.a s
flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Effect.as

Revision: 5473
Author: [email protected]
Date: 2009-03-20 16:02:58 -0700 (Fri, 20 Mar 2009)
Log Message:
Fix for bug around handling of constraints during and after effects were run, both for old and new effects. Fix was to correctly record and handle styles that were set or not set in either state and to temporarily set width/height values for the duration of an effect if we disabled the relevant styles that affect width/height.
QE Notes: None
Doc Notes: None
Bugs: SDK-17809
Reviewer: Jason
Testing: checkintests, Mustella Effects, ListDataEffects
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-17809
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/effects/effectClasses/FxAnimateInstance.a s
flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Effect.as

[svn:fx-trunk] 12865: Fix mx.controls.HTML and mx.core. FlexHTMLLoader so the participate in the current IME scheme

Similar Messages

Maybe you are looking for