v0.4.1

Changelog

• 78f2ce6: Fix changes is version 0.4 that introduced a bug causing JavaScript errors being thrown all over the place in fallback mode. It also adds a flag impress.supported that can be used in JavaScript to check if impress.js is supported in the browser.

v0.4.0

Changelog

• 811e045: Fix Firefox perspective
• 2131784: Configs data-perspective (in px, defaults so 1000), data-transition-duration (in ms, defaults to 1000)
• eb4df9c: Automatic scaling to fit window size, with configuration options data-width (in px, defaults to 1024), data-height (in px, defaults to 768), max-scale (defaults to 1), min-scale (defaults to 0)
  207c823: goto API function was renamed to stepTo because goto is a future reserved work in JavaScript, so please make sure to update your code
• 9d495ab: Fallback impress-not-supported class is now set on body element instead of #impress element and it's replaced with impress-supported when browser supports all required features
• 9d495ab: Classes step-ID used to indicate progress of the presentation are now renamed to impress-on-ID and are set on body element, so please make sure to update your code
• 5ff0398: Basic validation of configuration options
• e1786e3: Couple of typos and bugs fixed, courtesy of @gustaff-weldon
• 047c1c2: favicon added

UPGRADING FROM PREVIOUS VERSIONS

If in your custom JavaScript code you were using goto() function from impress.js API make sure to change it
to stepTo().

If in your CSS you were using classes based on currently active step with step- prefix, such as step-bored
(where bored is the id of the step element) make sure to change it to impress-on- prefix
(for example impress-on-bored). Also in previous versions these classes were assigned to #impress element
and now they are added to body element, so if your CSS code depends on this, it also should be updated.

Same happened to impress-not-supported class name - it was moved from #impress element to body, so update
your CSS if it's needed.

NOTE ON BLACKBERRY PLAYBOOK

Changes and fixes added in this version have broken the experience on Blackberry Playbook with OS in version 1.0.
It happened due to a bug in the Playbook browser in this version. Fortunately in version 2.0 of Playbook OS this
bug was fixed and impress.js works fine.

So currently, on Blackberry Playbook, impress.js work only with latest OS. Fortunately, it seems that most of the
users are quite quick with updating their devices

v0.3.0

Changelog

• 7b4393c: Fix Firefox 3D Bug that requires transform-style.
• 343299c: enable clicking on elements 'hiding' behind body in 3D
• cfe6448: Basic API to control the presentation flow from JavaScript
• db5857a: Add touch support
• 2b22ee3...2324484: Basic support for iPad (iOS 5 and iOS 4 with polyfills) and Blackberry Playbook

Breaking Changes

Because API was introduced the way impress.js script is initialized was changed a bit. You not only have to include impress.js script file, but also call impress() function.

See the source of index.html for example and more details.

v0.2.0

Changelog

• d8f70bd: Use strict mode
• 5ea857e: Yoda documentation added to the index.html file
• 65c456c / 8cd464a: Fixes laggy transitions in Chrome
• 11e5ddc: Add mousewheel event listener
• bb0113e: Disabled animation on the beggining of the presentation
• e968933: Clarify IE support

v0.1.0

First impressive release.

Contains basic functionality for step placement and transitions between them with simple fallback for non-supporting browsers.