Flash Player Pro is a handy flash tool kit designed as Macromedia flash player and manager. It has several powerful flash tools: preview and browse flash movie, capture flash image and set it as wallpaper, create flash screensaver with ease, make conversion between SWF and EXE flash movies etc. All of these features will help you enhance and extend the using possibility of existing flash files.
And with friendly user interface, Flash Player Pro offers you a fantastic animated flash world! With Flash Player Pro you can:. Watch tv shows, movies, music videos as well as local Flash video files.
Download flash movies from the Internet. Browse Adobe flash movies with built-in swf player.
View or play flash movies with built-in player. View or play movies in full screen model. Make flash screensaver with a few mouse-click. Make flash screensaver installer and distribute it with ease.
Capture flash movie image and save it. Capture flash movie image and set wallpaper. Build your own favorite folder, and browse flash movies in it. Make conversion between SWF and EXE flash movies. Copy or move flash movies to another folder.
Rename flash movies. Connect with.swf file extension. Update flash player to professional version. What's New:. Fixes the bug in non-administrator privilege account. Some minor improvements.
Contents. Features Adobe Flash Player is a runtime that executes and displays content from a provided file, although it has no in-built features to modify the SWF file at runtime. It can execute software written in the programming language which enables the runtime manipulation of text, data, and.
The player can also access certain connected hardware devices, including and, after permission for the same has been granted by the user. Flash Player is used internally by the (AIR), to provide a cross-platform runtime environment for and mobile applications. AIR supports installable applications on, and some mobile operating systems such as and. Flash applications must specifically be built for the AIR runtime to use additional features provided, such as file system integration, native client extensions, native window/screen integration, taskbar/dock integration, and hardware integration with connected and devices.
Data formats Flash Player includes native support for many different, some of which can only be accessed through the scripting interface. XML: Flash Player has included native support for parsing and generation since version 8.
XML data is held in memory as an XML, and can be manipulated using ActionScript. ActionScript 3 also supports (E4X), which allows XML data to be manipulated more easily. JSON: Flash Player 11 includes native support for importing and exporting data in the (JSON) format, which allows interoperability with and programs.
AMF: Flash Player allows application data to be stored on users computers, in the form of, the Flash equivalent to. Flash Player can also read and write files in the, the default data format for Local Shared Objects. Since the AMF format specification is published, data can be transferred to and from Flash applications using AMF datasets instead of or, reducing the need for and such data. SWF: The specification for the file format was published by Adobe, enabling the development of the SWX Format project, which used the SWF file format and AMF as a means for Flash applications to exchange data with server side applications. The SWX system stores data as standard SWF bytecode which is automatically interpreted by Flash Player. Another project, SWXml allows Flash applications to load XML files as native ActionScript objects without any client-side XML parsing, by converting XML files to SWF/AMF on the server. Multimedia formats Flash Player is primarily a graphics and multimedia platform, and has supported and since its earliest version.
It supports the following different multimedia formats which it can natively and playback. MP3: Support for decoding and playback of (MP3) audio was introduced in Flash Player 4. MP3 files can be accessed and played back from a server via, or embedded inside an SWF file, which is also a streaming format. FLV: Support for decoding and playing back video and audio inside (FLV and F4V) files, a format developed by and. Flash Video is only a container format and supports multiple different video, such as, and more recently. Flash Player uses hardware acceleration to display video where present, using technologies such as and to do so.
Flash Video is used by, and other news providers. FLV files can be played back from a server using, and can also be embedded inside an SWF file. Flash Video can also be streamed via using the or other such server-side software. PNG: Support for decoding and rendering (PNG) images, in both its 24-bit (opaque) and 32-bit (semi-transparent) variants. Flash Player 11 can also encode a PNG bitmap via ActionScript.
JPEG: Support for decoding and rendering compressed images. Flash Player 10 added support for the advanced image compression standard developed by, which results in better compression and quality than JPEG. JPEG-XR enables and compression with or without transparency. Flash Player 11 can also encode a JPEG or JPEG-XR bitmap via ActionScript. GIF: Support for decoding and rendering compressed (GIF) images, in its single-frame variants only. Loading a multi-frame GIF will display only the first image frame. Streaming protocols.
HTTP: Support for communicating with using requests and data. However, only websites that explicitly allow Flash to connect to them can be accessed via HTTP or, to prevent Flash being used as a tool for, and. Websites must host a certain XML file termed a cross domain policy, allowing or denying Flash content from specific websites to connect to them. Certain websites, such as, already host a cross domain policy that permits Flash content to access their website via HTTP.
RTMP: Support for live audio and video streaming using the (RTMP) developed. RTMP supports a non-encrypted version over the (TCP) or an encrypted version over a secure (SSL) connection. RTMPT can also be within requests to traverse that only allow HTTP traffic. TCP: Support for (TCP) Internet socket communication to communicate with any type of server, using.
Sockets can be used only via, and can transfer, or binary data (ActionScript 3.0 and later). To prevent security issues, web servers that permit Flash content to communicate with them using sockets must host an -based cross domain policy file, served on 843.
Sockets enable AS3 programs to interface with any kind of server software, such as. Performance Hardware acceleration Until version 10 of the Flash player, there was no support for acceleration. Version 10 added a limited form of support for on materials in the form of the API, but still did not have GPU-accelerated 3D vertex processing. A significant change came in version 11, which added a new low-level API called (initially codenamed Molehill), which provides full GPU acceleration, similar to. (The partial support for GPU acceleration in Pixel Bender was completely removed in Flash 11.8, resulting in the disruption of some projects like MIT's, which lacked the manpower to recode their applications quickly enough. ) Current versions of Flash Player are optimized to use for video playback and 3D graphics rendering on many devices, including desktop computers.
Performance is similar to playback. Also, Flash Player has been used on multiple mobile devices as a primary user interface renderer. Compilation Although code written in ActionScript 3 executes up to 10 times faster than the prior ActionScript 2, the Adobe ActionScript 3 compiler is a non-, and produces inefficient bytecode in the resulting SWF, when compared to toolkits such as., a toolkit that targets code to run within the Flash Player, uses the compiler to produce bytecode that runs up to 10 times faster than code the ActionScript 3 compiler produces, only because the LLVM compiler uses more aggressive optimization. Adobe has released ActionScript Compiler 2 (ASC2) in Flex 4.7 and onwards, which improves compilation times and optimizes the generated bytecode and supports, improving its performance at runtime. As of 2012, the multiplatform language can build programs for Flash Player that perform faster than the same application built with the Adobe Flex SDK compiler. Development methods Flash Player applications and games can be built in two significantly different methods:.
'Flex' applications: The Framework is an integrated collection of stylable, data manipulation and networking components, and applications built upon it are termed 'Flex' applications. Startup time is reduced since the Flex framework must be downloaded before the application begins, and weighs in at approximately 500 KB. Editors include and. Tetris theme a black midi. 'Pure ActionScript' applications: Applications built without the Flex framework allow greater flexibility and performance. Video games built for Flash Player are typically pure-Actionscript projects.
Various open-source component frameworks are available for pure ActionScript projects, such as MadComponents, that provide UI Components at significantly smaller SWF file sizes. In both methods, developers can access the full Flash Player set of functions, including, graphics, camera, microphone, and others. AIR also includes added features such as file system integration, native extensions, native desktop integration, and hardware integration with connected devices. Main article: In 2011, Flash Player had emerged as the de facto standard for online video publishing on the desktop, with adaptive bitrate video streaming, and fullscreen support. On mobile devices however, after refused to allow the Flash Player within the inbuilt web browser, Adobe changed strategy, enabling Flash content to be delivered as native mobile applications using the. Up until 2012, Flash Player 11 was available for the (ARM Cortex-A8 and above), although in June 2012, Google announced that Android 4.1 (codenamed ) would not support Flash by default.
Starting in August 2012, Adobe no longer updates Flash for Android. In spite of this, Adobe Flash is still available to install on Android devices via Adobe's update archives (up to Android 4.3). Flash Player is certified to be supported on a select range of mobile and tablet devices, from, (and ), and. As of 2012, Adobe has stopped browser-based Flash Player development for mobile browsers in favor of, however Adobe continues to support Flash content on mobile devices with the Adobe Integrated Runtime, which allows developers to publish content that runs as native applications on certain supported mobile phone platforms. Version 9 is the most recent version currently available for the Linux/-based // Internet tablets running OS2008, classic and Windows 95/NT.
Version 10 can be run under Windows 98/Me using. HP offers Version 6 of the player for. Other versions of the player have been available at some point for, and. The includes Flash Player. Adobe said it will optimize Flash for use on (ARMv7 and ARMv6 architectures used in the Cortex-A series of processors and in the ARM11 family) and release it in the second half of 2009. The company also stated it wants to enable Flash on, 3 and Samsung ARMs. Beginning 2009, it was announced that Adobe would be bringing Flash to via Media Processor CE 3100 before mid-2009.
Later said it welcomes the move of Flash, because 'it will transform mobile applications and it removes the claim that the desktop controls the Internet.' However, as of May 2009, the expected ARM/Linux devices had poor support for Web video and fragmented software base. Among other devices, provides Flash Player with their Leapster Multimedia Learning System and extended the Flash Player with touch-screen support. Sony has integrated Flash Player 6 into the 's web browser via firmware version 2.70 and Flash Player 9 into the 's web browser in firmware version 2.50.
Has integrated 3.1, equivalent to Flash 8, in the on the. The following table documents Flash Player and AIR support on: Platform Latest version 2.2–4.1, + Flash Player 11.1, AIR 3.1 2.1 Flash Lite 3.0 Flash Player 11.1, AIR 3.1.0–10.3.1 Flash Player 11.1, AIR 3.1 Flash Player 11.1, AIR 3.1 Flash Player 9.4 with Firmware 2.50, NetFront 2.81 Flash Player 9.1 (update 3) with Firmware 2.70 Flash Player 6 4.0 3.1 Flash Player 7 Flash Player 7 Other hardware Some CPU have been created for Flash Player, including, and the. They enable video games created for such platforms to run within Flash Player. Open source Adobe has taken steps to reduce or eliminate Flash licensing costs. For instance, the file format documentation is provided free of charge after they relaxed the requirement of accepting a to view it in 2008. Adobe also created the which removes licensing fees and opens data protocols for Flash.
Adobe has also open-sourced many components relating to Flash. In 2006, the (AVM2) which implements was donated as open-source to, to begin work on the virtual machine that will finally implement the language standard with the help of the community. It was released under the terms of a // and includes the specification for the ActionScript format; jointly managed by Mozilla and Adobe Systems It is now considered obsolete by Mozilla. In 2011, the was donated as open-source to the and rebranded as Apache Flex.
G4fancontrol 0.5. Some saw this move as Adobe abandoning Flex, and stepping away from the Flash Platform as a whole. Sources from Apache say that 'Enterprise application development is no longer a focus at Adobe. At least as Flash is concerned, Adobe is concentrating on games and video.' , and they conclude that 'Flex Innovation is Exploding!' The donated source code included a partly developed AS3 compiler (dubbed 'Falcon') and the set of technologies. In 2013, the C toolset was open sourced by Adobe and released on. The project was formerly termed 'Alchemy' and 'Flash Runtime C Compiler', and targeted the game development market to enable C video games to run in Adobe Flash Player.
However, Adobe has not been willing to make complete source code of the Flash Player available for development. Alternatives to the Adobe Flash Player such as and have been built, but are no longer under active development and therefore not a viable alternative. The only fully functional open-source third-party Flash Player is the commercially available Player, which is game development designed for integration into non-Flash.
Criticism Usability In some browsers, prior Flash versions have had to be uninstalled before an updated version could be installed. However, as of version 11.2 for Windows, there are now automatic updater options. Linux is partially supported, as Adobe is cooperating with Google to implement it via Chrome web browser on all Linux platforms.
Mixing Flash applications with HTML leads to inconsistent behavior with respect to input handling (keyboard and mouse not working as they would in an HTML-only document). This is often done in web sites and can lead to poor user experience with the site. The February 20, 2014 update to 12.0.0.70 introduced a reported bug, producing green video with sound only. This defect is related to hardware acceleration and may be overcome by disabling hardware acceleration via the Adobe settings in Firefox (accessed by right clicking within the video) or in Internet Explorer (within the Tools settings). This defect may be related to widely used graphics hardware, AMD Radeon HD video cards, and similar visual defects have occurred in earlier Flash updates, with the same workaround. See also: Flash Player supports persistent local storage of data (also referred to as ), which can be used similarly to or in. Local storage in Flash Player allows websites to store non-executable data on a user's computer, such as authentication information, game high scores or saved games, server-based session identifiers, site preferences, saved work, or temporary files.
Flash Player will only allow content originating from exactly the same website to access data saved in local storage. Because local storage can be used to save information on a computer that is later retrieved by the same site, a site can use it to gather user statistics, similar to how HTTP cookies and Web Storage can be used. With such technologies, the possibility of building a profile based on user statistics is considered by some a potential. Users can disable or restrict use of local storage in Flash Player through a 'Settings Manager' page.
These settings can be accessed from the Adobe website or by right-clicking on Flash-based content and selecting 'Global Settings'. Local storage can be disabled entirely or on a site-by-site basis. Disabling local storage will block any content from saving local user information using Flash Player, but this may disable or reduce the functionality of some websites, such as saved preferences or high scores and saved progress in games. Flash Player 10.1 and upward honor the settings in the latest versions of the Chrome, Firefox, Internet Explorer, and Safari web browsers, such that no local storage data is saved when the browser's privacy mode is in use.
Security. See also: Adobe security bulletins and advisories announce security updates, but Adobe Flash Player release notes do not disclose the security issues addressed when a release closes security holes, making it difficult to evaluate the urgency of a particular update. A version test page allows the user to check if the latest version is installed, and uninstallers may be used to ensure that old-version plugins have been uninstalled from all installed browsers. In February 2010, Adobe officially apologized for not fixing a known vulnerability for over a year. In June 2010 Adobe announced a 'critical vulnerability' in recent versions, saying there are reports that this vulnerability is being actively exploited in the wild against both Adobe Flash Player, and Adobe Reader and Acrobat. Later, in October 2010, Adobe announced another critical vulnerability, this time also affecting -based mobile devices. Android users have been recommended to disable Flash or make it only on demand.
Subsequent security vulnerabilities also exposed Android users, such as the two critical vulnerabilities published in February 2013 or the four critical vulnerabilities published in March 2013, all of which could lead to arbitrary code execution. 's Internet Security Threat Report states that a in and Flash Player was the second most attacked vulnerability in 2009. The same report also recommended using to disable Flash Player usage on untrusted websites. Predicted that Adobe software, especially Reader and Flash, would be primary target for attacks in 2010. Adobe applications had become, at least at some point, the most popular client-software targets for attackers during the last quarter of 2009. The Security Network published statistics for the third quarter of 2012 showing that 47.5% of its users were affected by one or more critical vulnerabilities. The report also highlighted that 'Flash Player vulnerabilities enable cybercriminals to bypass security systems integrated into the application.'
Steve Jobs criticized the security of Flash Player, noting that 'Symantec recently highlighted Flash for having one of the worst security records in 2009'. Adobe responded by pointing out that 'the Symantec Global Internet Threat Report for 2009, found that Flash Player had the second lowest number of vulnerabilities of all Internet technologies listed (which included both web plug-ins and browsers).' April 7, 2016, Adobe released a Flash Player patch for a memory corruption vulnerability CVE-2016-1019 that could be used to deliver via the Magnitude exploit kit. The vulnerability could be exploited for.
Vendor lock-in Flash Player 11.2 does not play certain kinds of content unless it has been digitally signed by Adobe, following a license obtained by the publisher directly from Adobe. This move by Adobe, together with the abandonment of Flex to Apache was criticized as a way to lock out independent tool developers, in favor of Adobe's commercial tools. This has been resolved as of January 2013, after Adobe no longer requires a license or royalty from the developer. All premium features are now classified as general availability, and can be freely used by Flash applications. Apple controversy.
Main article: In April 2010, at the time CEO of published an open letter explaining why Apple would not support Flash on the, and. In the letter he blamed problems with the 'openness', stability, security, performance, and integration of the Flash Player as reasons for refusing to support it. He also claimed that when one of Apple's computers crashes, 'more often than not' the cause can be attributed to Flash, and described Flash as 'buggy'. Adobe's CEO responded by saying, 'If Flash is the number one reason that Macs crash, which I'm not aware of, it has as much to do with the Apple operating system.' Steve Jobs also claimed that a large percentage of the video on the Internet is supported on iOS, since many popular video sharing websites such as YouTube have published video content in an compatible format, enabling videos to playback in mobile web browsers even without Flash Player. Release history. Macromedia Flash Player 2 (June 17, 1997).
Mostly vectors and motion, some, limited audio. Support of stereo sound, enhanced bitmap integration, buttons, the Library, and the ability to color changes. Macromedia Flash Player 3 (May 31, 1998). Added alpha transparency, licensed MP3 compression.
Brought improvements to animation, playback, and publishing, as well as the introduction of simple script commands for interactivity. Macromedia Flash Player 4 (June 15, 1999). Saw the introduction of MP3s and the Motion Tween. Initially, the Flash Player plug-in was not bundled with popular web browsers and users had to visit Macromedia website to download it; As of 2000, however, the Flash Player was already being distributed with all, and browsers. Two years later it shipped with all releases of. The install-base of the Flash Player reached 92 percent of all Internet users.
Macromedia Flash Player 5 (August 24, 2000). A major advance in ability, with the evolution of Flash's scripting abilities as released as ActionScript. Saw the ability to customize the authoring environment's. was the first initiative from Macromedia to separate design from content in Flash files. Generator 2.0 was released in April 2001, and featured real-time server-side generation of Flash content in its Enterprise Edition. Generator was discontinued in 2002, in favor of new technologies such as, which allows for seamless transmission of data between the server and the client, and Server. In October 2000, guru wrote a polemic article regarding usability of Flash content entitled '.
(Macromedia later hired Nielsen to help them improve Flash usability.). The old Macromedia Flash Player logo. Macromedia Flash Player 6 (version 6.0.21.0, codenamed ) (March 15, 2002). Support for the consuming Flash Remoting and Web Service (SOAP).
Supports ondemand/live audio and video streaming. Support for screenreaders via Microsoft Active Accessibility.
Added video for. Support for video, application components, shared libraries, and accessibility. Macromedia Flash Communication Server MX, also released in 2002, allowed video to be streamed to Flash Player 6 (otherwise the video could be embedded into the Flash movie). Macromedia Flash Player 7 (version 7.0.14.0, codenamed Mojo) (September 10, 2003). Supports progressive audio and video streaming. Supports ActionScript 2.0, an object-oriented programming language for developers. Ability to create charts, graphs and additional text effects with the new support for extensions (sold separately), high fidelity import of and 10 files, mobile and device development and a forms-based development environment.
ActionScript 2.0 was also introduced, giving developers a formal object-oriented approach to ActionScript. V2 Components replaced Flash MX's components, being rewritten from the ground up to take advantage of ActionScript 2.0 and object-oriented principles. In 2004, the 'Flash Platform' was introduced. This expanded Flash to more than the Flash authoring tool. 1.0 and 1.0 were released, both of which used the Flash Player as a delivery method but relied on tools other than the Flash authoring program to create Flash applications and presentations. Flash Lite 1.1 was also released, enabling mobile phones to play Flash content.
Last version for Windows 95/NT4 and Mac Classic. Macromedia Flash Player 8 (version 8.0.22.0, codenamed ) (September 13, 2005). Support for runtime loading of GIF and PNG images. New video codec ( ). Improved runtime performance and runtime bitmap caching. Live filters and blendmodes.
![]()
File upload and download abilities. New text-rendering engine, the. ExternalAPI subsystem introduced to replace fscommand. On December 3, 2005, Adobe Systems acquired Macromedia and its product portfolio (including Flash).
Except as expressly provided otherwise in an agreement between you and Adobe, all players are provided 'AS IS' without warranty of any kind, for testing purposes only. Distribution of these players is prohibited except as expressly provided otherwise in an agreement between you and Adobe. In no event is Adobe liable for any special, indirect, or consequential damages or any damages whatsoever resulting from the loss of use, data or profits, whether in an action for breach of contract or warranty or tort (including negligence) arising out of or in connection with the information or software. Adobe can change the information, software, and technical specification at any time and without notice.
This document addresses issues, primarily for Macromedia Flash MX 2004 developers, which are not discussed in the Macromedia Flash MX 2004 documentation or release notes. This document may be updated periodically as more information becomes available. Backward compatibility of newer versions of Flash Player with older Macromedia Flash file formats is a top priority for each new Flash Player version. One of the methods that Macromedia has used to ensure backward compatibility of Flash Player with Flash files created in older versions of Flash is through beta releases of Flash Player.
Ensure that you have the latest version of Flash Player installed by clicking to check the version. The current version of Flash Player 7 for Windows, Macintosh, and Linux operating systems is 7.0.69.0. The current version of Flash Player 7 for Solaris operating systems is 7.0.67.0. This release of Macromedia Flash Player includes features for delivering rich content and high-performance media such as video, support for industry standards such as Web Services/SOAP, XML and ECMA standards-compliant programming model as well as improvements to usability and workflow. Flash Player 7.0.14.0 also introduces an enhanced security policy.
The features in Macromedia Flash Player 7 are covered in detail in Flash Help in the Flash MX 2004 and Flash MX Professional 2004 authoring environment. Features that developers should be aware of include.
ID3 is meta information that is added to MP3 sound files and contains textual information such as the song name, album name and artist name. Most media players such as Winamp and others can display this information. Windows XP Explorer also has native support for ID3 and allows you to display the ID3 information in separate columns. In ActionScript Flash Player 7 will expose text tags.
ID3 V1 support is not touched. It will still be reachable through the old tags. If no IDV1 tag is present in the file Flash Player copies the IDV2 tags into the known IDV1 tag strings to provide backward compatibility. There are two methods added to the Movie Clip Object:. MovieClip.getNextHighestDepth. MovieClip.getInstanceAtDepth This feature provides listener callbacks that provide notification about the status of files being downloaded into movie clips. Downloading is initiated by the MovieClipLoader.loadClip command.
Adobe Flash Player 6.0 Download
The ActionScript PrintJob class expands upon previously available Flash Player printing features. It allows you to create content at runtime and print this content to multiple pages. The OS print dialog box appears only once and only one print job shows in the operating systems's list of print jobs. This feature improves the legibility and attractiveness of small Flash text.
There are no new ActionScript APIs to activate this feature. Flash Player 7 supports FLV progressive download (to a user's local drive) and playback without the need for a Flash Communication Server. Both HTTP and local file playback are supported. Control of the FLV is done through the NetStream object which allows you to play, pause, and seek the FLV. This feature allows Flash to flow html text around images in a seamless fashion similar to what is available in HTML.
This is a runtime-only feature; there is no Authoring component. You should include HTML image tags in your HTML text.
This feature allows access to additional metrics that allow you to create complex text layouts in ActionScript without using off-screen text fields. To properly align multiple controls so that all the text lines up, this feature allows access to font metrics that allow you to locate the text baseline. The Text Style Sheets feature is an implementation of a small subset of CSS, much like Flash's HTML text fields support a small subset of HTML. Cascading Style Sheets (CSS) is a simple mechanism for adding style information such as fonts, colors, and spacing to Web documents. This feature consists of two major pieces of functionality:. Enhancements to Flash Player's HTML text field feature, enabling it to associate with a new Style Sheet object that contains named TextFormat objects. A CSS style sheet loader and parser, which can load style sheets and apply them to text fields through the TextField.StyleSheet class and the TextField.styleSheet property.
Macromedia Flash Player 7 offers a capability to both notify users about the availability of new versions and install the latest version of Flash Player. The update mechanism is designed to provide Flash Player users with an easy and convenient mechanism to update their software in a timely and convenient manner. With the 7.0.14.0 release, the notification and update mechanism is available for users running on the Microsoft Windows platforms (98/ME, NT 4.0, 2000, XP) with Internet Explorer and AOL. With the 7.0.19.0 release, the notification and update mechanism is available for users running on the Microsoft Windows platforms (98/ME, NT 4.0, 2000, XP) with Mozilla, Netscape, or Opera. The update capability is available for the web players (when hosted by a browser). The debugging and standalone players do not offer this capability in version 7.0.14.0 or 7.0.19.0. Flash MX 2004 and Flash MX Professional 2004 content is now case sensitive.
This compliance is maintained on a per movie basis. If a strict Flash MX 2004 or Flash MX Professional 2004 movie calls a non-strict Flash 6 movie, the Flash 6 movie will remain non-strict. This feature allows you to force root to evaluate to the movie clip in which the problem content is loaded, rather than to the real root by creating a new property for the movie clip object, called lockroot. If lockroot is set to true on a movie clip, that movie clip acts as root for anything loaded into it.
Any movie clip, and any number of movie clips, may set lockroot to true. While the primary use is for an aggregator to set this property on a movie clip into which it is loading content, the lockroot property can be set either by the loading movie or the loaded movie. This feature includes a library that allows Flash Player to interact with a web service. This feature allows cross-movie scripting only between movies that originated from the exact same domain. Any other cross-movie scripting will only work after calling Policy Files (System.security.allowDomain) to permit access.
The changes in the Flash Player 7 security model can occasionally cause undesirable behavior in pre-existing content. Additional information can be located at the Flash Player site or at this.
Policy files are a feature that allows Flash Player to load data directly from any specified trusted domains and URLs. The changes in the Flash Player 7 security model can occasionally cause undesirable behavior in pre-existing content. Additional information can be located at the Flash Player site or at this.
This feature prevents cross-movie scripting when the calling movie is hosted on a non-HTTPS server and the movie being called is hosted on an HTTPS server. If you can't host all movies on an HTTPS server, which is the recommended solution, you can permit this kind of cross-movie scripting by calling System.security.allowInsecureDomain to permit access. We have expanded the array sorting API to support an expanded variety of options for sorting using Array.sort and Array.sortOn.
The ContextMenu and ContextMenuItem classes allos you to customize the context menu. You can add new menu items that trigger ActionScript methods and remove default items as desired. This feature adds the ability to catch and handle errors that occur in ActionScript and adds four keywords to the ActionScript language: try, catch, finally and throw. In all players, if the user right-clicks on a link, users will see the Link menu. This menu has two or three items and is not customizable. Menu Item: Behavior: Open exactly as if the user had clicked the link Open in new window (Browsers only) will always open a new window Copy link copies the URL of the link to the clipboard In the ActiveX Control and all Netscape plug-ins, the following browser-specific keys will open a link ina new window: Windows ActiveX - Shift-click Windows Netscape - Control-click Mac Netscape - Command-click Mouse Wheel support has been added, for Windows only. Mouse wheel support brings two benefits to Flash Player: Flash Player now, by default, scrolls text boxes vertically for all Flash movies (not only version 7 movies); and you can listen for mouse wheel events and respond appropriately.
This feature adds support for multi-tier dependent shared libraries. As of Flash Player 6.0.65.0, you can have a shared library that has its own shared library. With the 7.0.19.0 release, users on Netscape and supported Mozilla-based browsers will now be notified when a new version of Flash Player for users running on the Microsoft Windows platforms (98/ME, NT 4.0, 2000, XP) is available. The update capability is available for the web players (when hosted by a browser).
The debugging and standalone players do not offer this capability in either version 7.0.14.0 or 7.0.19.0. Flash Player now stores persistent shared objects in unpredictable locations. This improves client-side web security. Flash Player supports a new ActionScript API called System.security.loadPolicyFile. This enables cross-domain policy files to be placed in more flexible locations than was previously possible. Flash Player uses policy files as a permission mechanism to permit Flash movies to load data from servers other than their own. For more details on policy files, see: Flash Player 7.0.14.0 looked for policy files in only one location: /crossdomain.xml on the server to which a data-loading request was being made.
For an XMLSocket connection attempt, Flash Player 7.0.14.0 looked for /crossdomain.xml on an HTTP server on port 80 in the subdomain to which the XMLSocket connection attempt was being made. Flash Player 7.0.14.0 (and all earlier players) also restricted XMLSocket connections to ports 1024 and above. With this release of Flash Player, ActionScript can inform Flash Player of a non-default location for a policy file, using System.security.loadPolicyFile. For example: System.security.loadPolicyFile('This causes Flash Player to retrieve a policy file from the specified URL. Any permissions granted by the policy file at that location will apply to all content at the same level or below in the virtual directory hierarchy of the server.
Thus, continuing the above example: loadVariables('allowed loadVariables('allowed loadVariables('not allowed You can load any number of policy files using loadPolicyFile. When considering a request that requires a policy file, Flash Player always waits for the completion of any policy file downloads before denying a request. As a final fallback, if no policy file specified with loadPolicyFile authorizes a request, Flash Player consults the original default location, /crossdomain.xml. A new syntax allows policy files to be retrieved directly from an XMLSocket server: System.security.loadPolicyFile('xmlsocket://foo.com:414'); This causes Flash Player to attempt to retrieve a policy file from the specified host and port. Any port may be used, not only ports 1024 and above.
Upon establishing a connection with the specified port, Flash Player transmits, terminated by a null byte. An XMLSocket server may be configured to serve both policy files and normal XMLSocket connections over the same port, in which case the server should wait for before transmitting a policy file. A server may also be set up to serve policy files over a separate port from normal connections, in which case it may send a policy file as soon as a connection is established on the dedicated policy file port. The server must send a null byte to terminate a policy file, and may thereafter close the connection; if the server does not close the connection, Flash Player will do so upon receiving the terminating null byte. A policy file served by an XMLSocket server has the same syntax as any other policy file, except that it must also specify the ports to which access is granted. When a policy file comes from a port lower than 1024, it may grant access to any ports; when a policy file comes from port 1024 or higher, it may only grant access to other ports 1024 and higher.
The allowed ports are specified in a 'to-ports' attribute in the tag. Single port numbers, port ranges, and wildcards are all allowed. Here is an example XMLSocket policy file: A policy file obtained from the old default location - /crossdomain.xml on an HTTP server on port 80 - implicitly authorizes access to all ports 1024 and above. There is no way to retrieve a policy file to authorize XMLSocket operations from any other location on an HTTP server; any custom locations for XMLSocket policy files must be on an XMLSocket server. Because the ability to connect to ports lower than 1024 is new, a policy file loaded with loadPolicyFile is always required to authorize this, even when a movie is connecting to its own subdomain.
This release of ActiveX Flash Player supports a new HTML parameter called SeamlessTabbing. The default value is true; set this parameter to false to disable 'seamless tabbing', which allows users to use the Tab key to move keyboard focus out of a Flash movie and into the surrounding HTML (or the browser, if there is nothing focusable in the HTML following the Flash movie). ActiveX Flash Player has supported seamless tabbing since version 7.0.14.0. Disabling seamless tabbing restores the tabbing behavior of Flash Player 6, in which tabbing from the end of the tab order inside a Flash movie wraps the focus back to the first focusable object in the Flash movie. Here is an example of disabling seamless tabbing:. Text entry using the Korean IME on Korean systems can now be performed inline without requiring a separate text entry box.
Mouse Wheel events can now broadcast to Mouse listeners when movies are published for Flash Player 6 SWFs. Performing the Array.sortOn operation using both 'UNIQUE' and 'NUMERIC' options results in unsuccessful completion. Four changes have been made to optimize memory usage. Six known stability issues have been fixed. String.split will delete the last element if it begins with the same characters as the delimiter. Carriage returns don't translate inside Flash (Mac only). Shared object deletion fails for subdirectories (Mac only).
AMF responses are dropped by the player when making multiple simultaneous requests. XML incorrectly parses escaped strings. The debug player can't display Kanji using standard fonts. In the Korean IME, the first word typed is duplicated in the lower right portion of the screen. When Character options include Non-Latin glyphs you can't enter non-Latin text. Double-byte data received through web service is corrupted.
![]()
'Locals' tab often shows no content even though there are local variables present. Flash Player in various browsers shows incorrect version information. Flash Player 7 lists duplicate variables from Flash Player 6 movies that differ only by case.
Macintosh OS X Plug-in Bundle With this release, Flash Player takes advantage of Apple's bundling technology and provides the OS X Flash Player plug-in in a bundle, a single directory that contains executable code and resources related to the code. The Flash Player plug-in on OS X has been renamed from 'Shockwave Flash NP-PPC' to 'Flash Player.plugin.' Macromedia Flash Player 7.0.25.0 for Linux includes all of the features from Flash Player 7.0.19.0 except for windowless mode. Macromedia does not officially support specific cameras or sound drivers on the Linux platform. However, we tested Flash Player 7.0.25.0 with Logitech Quickcam Express web camera, Standard Microphone, and Creative Sound Blaster was used.
Issues for Flash Player 7.0.25.0: Linux. In the Mozilla browser, the Ctrl+N command doesn't work when Flash content is playing. User can't type or delete when cursor is outside of the area of the running SWF. User can't type in text field when mouse is over another SWF. The onKeyDown and onKeyUp event handlers don't work in the Konqueror browser ( ). Flash content does not print symbols at less that 100% alpha.
Motion Status remains the same even when motion is demonstrated for the Camera. The Konqueror browser sometimes asks the user to specify the directory path where the plug-in is located. Macromedia Flash Player 7.0.53.0 for Solaris includes all of the features from Flash Player 7.0.19.0 except for windowless mode.
Macromedia does not officially support specific cameras or sound drivers on the Solaris platform. Issues for Flash Player 7.0.53.0: Solaris. In the Mozilla browser, the Ctrl+N command doesn't work when Flash content is playing. Text field still show focus when the focus is actually on another object. Flash does not print vectors ignoring the alpha. Flash Plugin on Solaris loses audio/video sync.
Macromedia Flash Player 7.0.60.0 and Macromedia Flash Player 7.0.61.0 include security enhancements described in for operating systems that are not supported by the Flash Player 8 release. Macromedia Flash Player 7.0.63.0 includes security enhancements described in for operating systems that are not supported by the Flash Player 8 release. This update introduces additional version checking to the installation process. Because older installers and controls do not contain the new version checking logic, the Flash Player control is locked upon installation. Starting with this update, installers and uninstallers from Adobe are designed to work with this change, and there is no impact to the end-user installation experience. Flash and Flex developers may need to make slight modifications to their normal methods of switching between player versions during testing to account for this change.
This is described in. Adobe Flash Player 7.0.66.0 and 7.0.68.0 include security enhancements described in for operating systems that are not supported by the Flash Player 9 release. Adobe Flash Player 7.0.67.0 and 7.0.69.0 include security enhancements described in for operating systems that are not supported by the Flash Player 9 release. Adobe Flash Player 7.0.70.0 includes security enhancements described in for operating systems that are not supported by the Flash Player 9 release. Adobe Flash Player 7.0.73.0 includes security enhancements described in for operating systems that are not supported by the Flash Player 9 release.
Please send the detailed bug information via the online form. Note: Due to the high volume of email we receive, we are unable to respond to every request. Thank you for using Macromedia Flash Player, and for taking the time to send us your feedback!
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |