jPlayer 1.0.0 Release notes

• Fixed major Bug: All calls to jPlayer are now passed through a single plugin method called jPlayer(). This breaks backwards compatibility and developers are advised to review the new documentation for the new control mechanism.
• Fixed major bug: Fixed the problem where some browsers were not always detecting the end of the MP3 file in Flash. Used the Flash Sound.onSoundComplete to raise a flag, which is then captured by the progressBroker(). The values affected by the inaccurate Sound.position property are forced to their correct values. (Affects: playedTime, playedPercentRelative and playedPercentAbsolute.)
• Fixed major bug: Using playHead, playHead or stop immediately after a setFile when the browser is using HTML5 native audio, now works and does not throw an exception.
• Fixed major bug: Local server testing on Firefox 3.6 developed a problem when inserting the Flash SWF file into the webpage. This caused the SWF to be loaded twice for an unknown reason. A 100ms delay was added to the initialization of the ExternalInterface.addCallback() declarations and the jPlayerReady signal. This solved the problem with local testing on Firefox 3.6.
• Fixed minor bug: Event functions default to an empty function. Developer defined functions are checked that they are a function, otherwise an alert box will notify of the problem (when {warningAlerts:true}). Affects the constructor ready() function, onSoundComplete() and onProgressChange().
• Fixed minor bug: Corrected the HTML5 jPlayer.play event code in IE, setInterval(function, time, argument), since IE only supports setInterval(function, time). (IE does not supports HTML5 at the moment.)
• Fixed minor bug: When in an HTML5 browser, the setFile command caused the audio file to be pinged before a play command was given. This has been fixed so that the audio file will not be touched until a play command is given.
• Fixed minor bug: When in an HTML5 browser that supports HTMLMediaElement.buffered.end(), such as Safari 4, stopping or pausing jPlayer while the download was in progress would freeze the load bar. This fix allows the load bar to function correctly, irrespective of whether jPlayer is playing or not.
• Method renaming: jPlayerId method renamed to cssId to match data structure.
• Removed Feature: Removed the bufferMsg method and associated code, since this feature was only supported when the Flash component was used.
• Removed feature: Hover states are no longer managed through the jqjp_hover class. Originally added to correct IE6 :hover not working correctly. All hover states should now be defined using standard :hover CSS.
• Removed feature: Buffer state is no longer managed through the jqjp_buffer class on the load bar. The original feature would only work when Flash was being used. The feature was removed so that the HTML5 and Flash solutions are identical.
• New feature: jPlayer now has default CSS Ids built into it. Added customCssId constructor option to control whether the default CSS Ids are used. See documentation for more information. (Default: {customCssId:false}
• New feature: Added nativeSupport constuctor option to force jPlayer to use the Flash component. (Default: {nativeSupport:true})
• New feature: Added errorAlerts and warningAlerts constructor options to help debug jPlayer projects. (Default: {errorAlerts:false, warningAlerts:false}
• New feature: Added graphicsFix constructor option to allow the hidden random number text to be disabled. The random number is used to fix graphical update problems with Safari and Chrome browsers.
• New feature: All jPlayer configuration information is available via jPlayer("getData", dataName) method. This includes new diagnostic information such as whether jPlayer is playing a track or not. For advanced users, read/write access is provided through $("jpId").data("jPlayer.config"). See documentation for full details.
• New feature: Changed swfPath logic to accommodate a trailing slash on the path. Eg. {swfPath: "myDir"} is the same as {swfPath: "myDir/"}.
• New feature: Calls to the Flash are now in a try/catch statement. If the function fails, an alert notifies the developer (when {errorAlerts:true}) that there is a problem with the swfPath and/or Jplayer.swf file location.
• New feature: The final call of onProgressChange happens after all internal configuration data has been updated. When onSoundComplete occurs, onProgressChange is called once afterwards. The HTML5 and Flash solutions mirror this sequence.
• Code quality: Refactored code to remove all eval() statements.
• Code quality: Unbound internal events when a new cssId is given. (Note: cssId was formerly jPlayerId.)
• Code quality: jQuery selectors are stored internally, so that they are only called once. (Improves performance.)