Releases: futurepress/epub.js
Releases · futurepress/epub.js
Updated Dependencies
- Updated RSVP, JSZip, localForage, Jquery
- Removed Underscore
- Fixed Android not loading when
status === 0
Enable loading books cross domain
- Chapter
render
and `load' methods get chapter contents via ajax - Moved url replacement hooks to Chapter
render
method - Renderer displays contents with
document.write
into iframe
Offline Storage, Locations, Optional Xpath
- Implements offline storage using localForage.js
- Adds Locations for getting location and percentage information from a book
- Only uses xpath when available, falls back to evaluating xpaths on rendered document.
Continuous Rendering
Alpha Version of Continuous Rendering
Mobile Browser Detection
Added detection to switch to setLeft to use transform on mobile browsers.
Add RTL Support
Adds support for RTL languages
- Detects
page-progression-direction
on spine element - Updates
pageMap
to support RTL - Switches render page direction on RTL
- Reader switches arrow functionality if direction is RTL
- Added example/rtl.html using https://code.google.com/p/epub-samples/downloads/detail?name=israelsailing-20130127.epub as an example
Many bug fixes, Replace Zip.js with JSZip
- Replace Zip.js with JSZip, seems very stable but perhaps a little less efficient without the worker scripts
- Fixes relative links per #152
- Supports nav item with multiple properties, per #124
- Handles blob link in URI
- Only assign book.cover if coverPath is available, per #158
- Added fallback to find body element, per #159
- Make ncx media-type fault tolerance per @shenzhuxi #165
- Merge pull request #169 from bielskij/master which fixes cfi generation
Updates to reformating, spine navigation, bug fixes
- Fixes critical issue with spine navigation
- Fixes page maps when reformatting (changing css, orientation, and size)
v0.2.1 - Page Maps
Page maps contain CFI's for start and end of each page.
These are now generated on chapter load and used for navigation and pagination in each chapter.
Better CFI handling by translating to XPath on the content document.