This article contains a list of current known issues for Adobe Edge Animate CC. If you have questions that this article doesn't answer, see the Edge Animate Help & Support page and the Edge Animate community for additional assistance.

Update to Edge Animate CC 2014 Release (October 2014)

  • Sometimes, upgrading compositions created in versions earlier than Edge Animate CC 2014 release fails. (3831007)

Workaround: Open these compositions in Edge Animate CC 2014 and save them. You can then open them in the latest update to upgrade them.

  • Event listeners are not removed if the jQuery 'off' is used. (3830972)
  • Selection rectangles are not correctly displayed for children of parent elements that have  the borderwidth set. (3831090)
  • Elements that have no 'transform' assigned to them do not respond as expected if they have siblings that are transformed. This issue occurs because of some issues on a few versions of web browsers. (3833417)

Workaround: Edit the project HTML to add the following style after <!--Adobe Edge Runtime End-->

		.EDGE-443268152 * {
			-webkit-transform: translateX(0px);

Change the composition ID accordingly for your project.

Edge Animate CC 2014 Release (June 2014)


    Muted, volume, and playbackRate properties are not supported on iOS and other mobile devices due to device limitations. (3637501)
    For audio volume and muting, control is left entirely to the user to adjust on the device itself.
    Autoplay property for an audio element is not supported by iOS and most other mobile devices due to device limitations (to prevent automatic addition of unwanted data charges). (3618495)
    Preloading is also not supported on most mobile devices for the same reason. Instead, add a play command to a user event, such as touchstart.
    Most AAC files do not play back in the Animate timeline. (3628062)
    However, they should play back in browsers that support the AAC format (Safari).

Responsive Layout

    Coordinate layout control in the Properties panel does not update if an element with any transition on it does not also have a position transition. Clicking the control doesn't appear to take. (3695098)
    Workaround: reposition the element and then undo the reposition, or convert the element to a symbol before you change its coordinate space.
    Webkit (Safari, Chrome) browsers-only: Responsive scaling with symbols breaks element z-order when viewport is larger than the Stage. (3632270)
    A poster image taken of a larger composition (greater than 800px wide) that is set to percentage-based layout will have incorrect size. (3691174)
    Workaround: Set layout units back to pixels, take the poster image, and then reset them to percentage units.
    Images and webfonts in a responsive composition can get blurry when scale is applied and your resize the browser. (3637583)
    Browser limitation

Browser-related issues

    Chrome: Clipping may occur in browser when a transformed element has a filter applied. (3494343)
    Kindle browser does not display web fonts. (3499262)
    Browser limitation.
    When corner radius is applied to a parent element with overflow set to hide, the child will not be clipped at the parent corners in Safari and Chrome browsers. (3474126)
    Workaround: if the child element is an image, changing from a div to img tag will render it correctly.
    IE9: images that are rotated don't display the correct positioning in IE9. (2951716)
    Browser limitation.
    IE9: nested symbol rotation is rendered incorrectly in IE9. (3025319)
    Browser limitation.
    Images that are rotated to negative values don't render correctly in IE9. (2929903)

Publish issues

    Edge Web Fonts and Typekit fonts are not rendered when published to iBooks. This occurs because they must be loaded from a domain over HTTP, and are not when viewed from an iBook. (3496140)
    Workaround: use local fonts or Google Web fonts when exporting to iBooks.


    Drop shadow CSS filter does not render outside of element bounds if the element has less than 100% opacity. (3475948)
    Workaround: use box shadow, or lower opacity on the element, convert it to a symbol, and then apply the CSS drop shadow filter to the symbol instance.
    Eyedropper tool does not sample colors outside of stage boundaries. (3691963)
    Also, elements on the main Stage cannot be sampled from a symbol sub-stage.
    Position transitions do not play back on the Animate Stage when CSS-filter blur or drop shadow is also applied. (3681275)
    These transitions do play back correctly in Webkit browsers.
    Windows only: importing an asset that has a path/filename length greater than 260 characters will raise an exception on import into Animate. (3638845)
    Workaround: Save composition elsewhere so it has a shorter total path length, or if the asset has a very long name, shorten it in Explorer before importing it.
    Stage is sized too small when placed in a static page within an element that has no width and height defined. (3637608)
    Workaround: explicitly set the parent element width.

Security considerations when opening Animate projects from your desktop

    Animate uses an HTTP server to deliver content to your browser when using Preview in Browser. Animate serves files under any directory that contains an open Animate composition. To help avoid making sensitive files accessible via the server in Animate, we recommend that you save Animate compositions in their own folder.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy