Accessibility

Flex Release Notes

Flex Release Notes

This document contains the following information about the Macromedia Flex 1.0 release:

Installing the Flex 1.0 Updater 1

After installing Flex 1.0, you should install Flex 1.0 Updater 1. The Flex 1.0 Updater 1 includes performance and reliability improvements, enhanced documentation for the "Flex ActionScript and MXML API Reference", and more.

Documentation Updates

This section describes topics that are not currently in the Flex 1.0 documentation.

XSD file

The MXML schema defines the structure of your MXML files, including the contents of each element and the constraints on the values of those elements. Flex includes an XSD file that you can integrate with your third-party editing tools for schema validation and easier MXML coding. This file is installed in the following location:

{install.dir}/extras/schema/mxml.xsd

Bootstrap classloader

Normally, all Flex classes are loaded by the Flex bootstrap classloader to avoid mismatches with application server classes. When the Flex classloader does not find a class, it delegates to the application server's classloader. One known issue, however, exists for complex input argument types used in Macromedia Flash Remoting. This can cause a problem because the Flex Flash Remoting gateway servlet is loaded by the Flex bootstrap classloader, but the complex type translated from ActionScript might be loaded by the application classloader.

To avoid any class mismatches, ensure that your complex type classes are in the Flex bootstrap classloader's classpath. This path is set by the flex.class.path context parameter in your web application's /WEB-INF/web.xml file. To add additional entries, separate them with commas; for example:

<context-param>
 <param-name>flex.class.path</param-name>
 <param-value>../../classes,./WEB-INF/flex/jars</param-value>
</context-param>

Disabling browser detection and deployment for Microsoft Internet Explorer

The Macromedia Flash Player <enable> tag in the flex-config.xml file only enables and disables player detection for non-Microsoft Internet Explorer browsers. This tag does not disable player version detection and download for Internet Explorer browsers.

To prevent Internet Explorer from triggering a player update, you can set the required version to an arbitrarily low value such as 4.0.0; for example:

    <flash-player>
        <required-version>4</required-version>
        <required-major-revision>0</required-major-revision>
        <required-minor-revision>0</required-minor-revision>
    </flash-player>

Enabling directory browsing

When installing Flex with the integrated JRun Java Application Server, directory browsing is disabled by default. To enable directory browsing, set the browseDirs parameter to true in the jrun_root/servers/server_name/SERVER-INF/default-web.xml file; for example:

 <servlet>
   <servlet-name>FileServlet</servlet-name>
   <servlet-class>jrun.servlet.file.FileServlet</servlet-class>
   <init-param>
     <param-name>browseDirs</param-name>
     <param-value>true</param-value>
   </init-param>  
 </servlet>

Known Issues

This section describes known issues in this release.

File-naming issues

Flex has the following restrictions on filenames:

  • It is possible to have an MXML file and an ActionScript file share the same name in the same directory. For example, you can include foo.as from within foo.mxml. However, you cannot have an MXML file and an ActionScript component in the same directory with the same name.
  • You should not use Flex class names or reserved words as filenames. For example, do not create a file named Button.mxml. For a complete list of Flex class names, see Flex ActionScript and MXML API Reference.

Open issues

Flex has the following open issues:

51461 You cannot make hypertext links in MXML application text controls, except when using the Link control, as the following example shows:
<mx:Link label="Macromedia" click="getURL('http://www.macromedia.com')" />
        

73758 CSS type selectors in two MXML components override each other. Flex honors the styles set by the last-instantiated component.

73929 The Opera 7.11 browser supports MXML files only when JavaScript is not enabled.

74113 You cannot use the <mx:Binding> tag within the <mx:Repeater> tag.

74581 Changing the colSpan or rowSpan properties of a GridItem inside a Grid control at runtime does not cause a layout change. To work around this issue, call the invalidateLayout() method of the Grid; for example:

myGrid.invalidateLayout();
        

75170 Flex does not start on Tomcat 5.x. To work around this issue, use JDK 1.4.x or copy the xmlParserAPIs.jar and xercesImpl.jar files from flex/WEB-INF/jars directory into the tomcat/common/endorsed directory.

75839 If you stop a debugging session, and then restart the debugger, you must also close your Microsoft Internet Explorer window and reopen it. To work around this issue, select the Reuse Windows for Launching Shortcuts option in Internet Explorer.

77381 Browser bookmarks from browsers other than Internet Explorer that point into an MXML application always returns to the start of the MXML application and not the bookmarked location within that application.

77383 Some application servers do not support finding resource files when the case in the URL does not match that of the underlying file system. For example, a reference to the file someDirectory/image.jpg is not found as somedirectory/image.jpg.

79445 With dynamic download of SWF files, the loading file must be in the same directory as the file whose SWF file is being loaded, or you should use absolute paths.

79449 You must define all cursors in the top-level application file, but you can put the code that changes the cursor anywhere in the application. If two applications are running at the same time, the last cursor change takes effect for both applications.

79925 Data binding does not work with a SharedLocalObject. To work around this issue, write a wrapper object that uses a SharedLocalObject internally, but has getters and setters that the rest of your application can use. You then declare and dispatch the appropriate events to update the SharedLocalObject.

80137 You cannot set different label styles for different layouts inside the TabNavigator and Accordion containers.

80625 An application wrapped in an iframe tag that is the same width and height as the IFrame can cause scroll bars to appear when the application runs on Internet Explorer on a Macintosh. The cause is that some space is used by the IFrame's border and other padding. To work around this issue, make your application a few pixels smaller than the iframe that contains it.

80721 Accessibility only works with the released version of Macromedia Flash Player.

81132 In Internet Explorer on a Macintosh, the TabBar container does not respond to the Page Up, Page Down, Home, and End keys.

81844 When you bind a value to the contentPath property of a media component, and then bind contentPath property to a TextArea control, the TextArea control does not update properly.

82041 Flex displays a blank SWF file when you request a file that contains errors using the .swf filename extension. For example, when using http://baseurl/template.mxml.swf to request a file with an error, Flex displays a blank page in the browser. Flex writes compilation errors in the system log regardless of how the file was requested.

82592 Installing Flex on double-byte operating systems requires that you install a double-byte Java runtime before running the Flex installer.

85026 Flex cannot process a non-UTF-8 encoded XML file using the HTTPService tag.

85869 When running on systems using UTF-8 encoding, Flex debugging information that is output to the console appears unreadable unless the operating system's System.out calls support UTF-8 encoding. The workaround is to read the entries in the log file rather than the console.

86453 The TextArea control's <mx:htmlText> child tag does not support embedded fonts.

86709 If you have a Form container that includes a default button, that default button's click event is triggered when the user presses the Enter key, even when the button is disabled.

86767 When using the fdb command-line debugger, if fdb opens an MXML file that contains other MXML files, refreshing the browser might stop the application. The workaround is to debug the MXML files individually.

86832 Flex applications in Netscape Navigator 4.8 appear at a small size (50 by 50 pixels). To avoid this issue, explicitly set the application's height and width properties.

86947 The MXML compiler will not compile files that import large models at compile time. Use HTTPService to load models using XML or other external files at runtime.

87024 You cannot dynamically change the layout direction if the Box container has an explicit width and height. To avoid this issue, do not explicitly define dimensions for the Box container or set the widthFlex and heightFlex properties to 1.

87102 A change in the Flex cookie format between Beta 3 and the final release can cause a "Could not parse cookie hash value" error. This error has no visible effect. You can avoid it by deleting the client browser's cookie files and reloading the page. This only affects client machines on which you installed the Flex Beta.

87109 The Array.push() method sometimes fails to provide the data for a dataProvider of data-driven components such as the ComboBox control. To avoid this issue, use the addItem() method.

87176 The <mx:Loader> and <mx:Image> tags temporarily load images at their actual size, then sets them to the correct size, even when the height and width properties are explicitly set. This bug affects all client browsers except Microsoft Windows Explorer. The workaround is to make them invisible while they are loading by adding the following to your <mx:Loader> and <mx:Image> tags:

visible="false" complete="event.target.visible=true"
        

This workaround does not work for the Opera browser.

87232 Flex does not support accessing EJBs with RemoteObjects because it uses the mx.rpc.RemoteClassRelayResponder class to preprocess results and, as a result, causes a stack overflow for proxy objects returned for EJB create methods. The workaround is to use the FlashRemoting ActionScript API and the mx.rpc.RelayResponder class.

87279 You must reference custom rowRenderers in your code so that Flex includes them in your application. If your custom rowRenderer does not appear, add a variable declared as the type of the custom rowRenderer; for example:

<?xml version="1.0" encoding="iso-8859-1"?>
<mx:Application xmlns:mx="http://www.macromedia.com/2003/mxml" verticalGap="0">
	<mx:Script>
		static var rowRenderImport=MyRowRenderer;  // explicitly declared custom rowRenderer
	</mx:Script>
	<mx:Array id="myData">
		... // your data
	</mx:Array>
	<mx:Panel>
		<mx:List dataProvider="{myData}" rowRenderer="MyRowRenderer" />
	</mx:Panel>
</mx:Application> 
        

87284 When a <mx:WebService> or <mx:RemoteObject> that is a child of any MXML component produces an error, the error alert does not appear during runtime. The workaround is to define a fault handler in the <mx:WebService> or <mx:RemoteObject> tag, and explicitly display an alert; for example:

<mx:WebService id="myService" wsdl="myWSDL" fault="mx.core.Application.alert(event.fault.faultstring);" /> 
        

87317 When defining a service in the flex-config.xml file, Flex does not enforce the value of the <allow-unnamed-access> tag when you use {context.root} as part of the service's endpoint URL; for example:

<service name="SampleSalaryWS">
 <wsdl>{context.root}/services/SalaryWS?wsdl</wsdl>
 <endpoints>
  <endpoint>{context.root}/services/SalaryWS</endpoint>
 </endpoints>
 <allow-unnamed-access>false</allow-unnamed-access>
</service>
        

If your unnamed whitelist allows this service, you can still access the service's WSDL URL with the flashproxy using a URL similar to the following:

http://localhost:8100/samples/flashproxy?target=http://localhost:8100/samples/services/SalaryWS?wsdl
        

The workaround is to specify WSDL and endpoint URLs in the service definition rather than use the {context.root}.

87332 The <mx:HTTPService> tag does not send data on Tomcat when the method is POST, noProxy is false, and contentType is application/x-www-form-urlencoded. The workaround is to set the method to GET, noProxy to true, or contentType to another allowed value.

Getting Started

 

Application Development

 

Security

 

Downloads

 

Documentation

 

Community Resources