Accessibility

Release notes for Adobe AIR developers 2.0.3

Release date: 8/10/2010

Getting started

Welcome to the developer release notes for Adobe AIR 2.0.3. This update includes fixes that improve the security, stability, performance, and compatibility of AIR.

Please refer to the Adobe AIR 2 release notes for additional information.

System requirements

For the current Adobe AIR system requirements, please visit: http://www.adobe.com/products/air/systemreqs/

Version information

Flash Player plug-in

AIR 2.0.3 includes an updated version of the Flash Player plug-in (10.1.82.73), which is used when displaying SWF content embedded in HTML. For more information, see http://www.adobe.com/support/documentation/en/flashplayer/releasenotes.html.

Changes in AIR 2.0.3

AIR 2.0.3 is a runtime-only release

Continue to use the AIR 2.0.2 SDK to develop AIR applications. An SDK corresponding to the AIR 2.0.3 runtime will not be released.

To verify that a bug in your application was fixed in AIR 2.0.3, you can install the AIR 2.0.3 runtime. Use the ADL -runtime parameter to debug under AIR 2.0.3 (see Using the AIR debug launcher for more information).

Support for HTTP response compression on Windows

AIR applications on Windows can now accept HTTP responses compressed with GZIP or Deflate. By default, AIR includes the header "Accept-Encoding: gzip, deflate" with every HTTP or HTTPS request. If the server is configured to compress the response data, network performance is improved. HTTP response compression has been available for Mac and Linux since AIR 2.0.2. Automatically compressing the HTTP request data sent by the application to the server is not supported.

Applications must use the AIR 2 (or later) namespace in the application descriptor file to take advantage of HTTP response compression.

Change in timer behavior

In previous versions of AIR and Flash Player, timers did not restart the timer interval until any code triggered by the timer finished executing. Thus, if you created a timer to repeat every 500ms, and it took 200ms to execute the code in your timer event handler, then the timer would actually dispatch a timer event every 700ms.

As of AIR 2.0.3 and Flash Player 10.1, timers now restart the timer interval immediately. Thus a timer with a repeating interval of 500ms will now fire every 500ms, regardless of how long the code triggered by the timer event handler takes to execute.

This change can cause the timers in your application to dispatch timer events more frequently than before. Because the code triggered by the timer is run more frequently, the overall CPU utilization of your application may increase. If this increase is significant for your application, increase the intervals assigned to the timers in your application to compensate.

All AIR applications that use timers may be affected by this change when run with the AIR 2.0.3 runtime.

Security improvements

Adobe AIR 2.0.3 includes security improvements described in Security Bulletin APSB10-16.

Resolved issues

Issue # Title
2637551 Improved fullscreen rendering performance
2635243 Using De MonsterDebugger to debug an application no longer causes the application to quit unexpectedly
2648625 IME input is now correctly enabled when changing focus programmatically after changing an edit field type from dynamic to input
2640681 BrowserInvokeEvent.BROWSER_INVOKE is no longer fired twice when an application is launched from the browser via the install badge
2644277, 2649149, 2650433

In some cases, mouse tracking and response to keyboard input were delayed (Windows only)

2636304, 2643332 The mouse position did not refresh under heavy CPU load
2616416, Jira FP-4769 The BitmapData::copyPixel() method executed more slowly than in AIR 1.5
2629777 Non-embedded, transparent FTE text did not print correctly when using bitmap printing (Windows only)
2641584 Accented characters did not retain their accents when typed using dead keys (Linux only)
2575737 URLMonitor did not dispatch a status change event when the network connection changed (Linux Only)
2632803 When the globalRuntime.conf file was present, installing an AIR application resulted in the installer quitting unexpectedly
2630349 Content rendered by WebKit now uses the DeviceRGB profile instead of the GenericRGB profile, for consistency with Safari (Mac OS only)
2643787 Using WebKit, XML streams containing multi-byte Unicode characters could result in the parsing being terminated prematurely
2656705 The WebKit getElementsByTagName() method did not return video elements in the page DOM

Known issues

Camera resolution limit on Linux

Camera resolution cannot be increased beyond 320x240 on Ubuntu Linux (2586239)

Crash when typing characters with an IME when focused on a non-editable component

Typing characters with an IME when focused on a button or other non-editable component can cause an application to quit unexpectedly. (Linux only) (2650465)

Feedback

To report a feature request, please submit and vote on ideas using the Adobe AIR Ideas website.
To report a bug, please report the issue using the Adobe AIR feedback bug feedback form.