search

e-alfred / epubreader

EPUB/CBR/PDF reader app for Nextcloud
GNU Affero General Public License v3.0
80 stars 21 forks source link

Cannot page forward to next chapter #5

Open spiraldancing opened 4 years ago

spiraldancing commented 4 years ago

Running the new Reader (1.4.2) on Nextcloud 18.0.4, viewing epub books through Firefox 76.0 on Linux Ubuntu (20.04) laptop.

Paging forward and backward "sticks" in places, requiring 2-3-4 clicks or arrow-presses to advance to the next/previous page.

Seems to always happen at chapter divisions. Paging forward from end of Chapter n to start of Chapter n+1 is impossible. I must open the Table of Contents slider and select the next Chapter to advance. Paging backwards sometimes works after 2-4 clicks, sometimes not, requiring TOC navigation.

It looks like this is a brand new clone of the old no-longer-supported Reader. Thanks for reviving it.

spiraldancing commented 4 years ago

Hmm ... Update.

It is definitely Firefox-specific ... and, yes, I do have a bunch of plug-ins and add-ons, but I think I have them all disabled and turned off and still seeing this.

In Chromium (no add-ons or plug-ins at all), paging across Chapters is not an issue ... however:

I am specifically looking at 3 books. All 3 books open in FF, all 3 books exhibit the same "can't page past Chapter 1" issue.

However, in Chromium, I can open the 1st book, and page through it without any problem ... however, books 2 and 3 do not open at all. I just get an eternal spinning wheel showing that it's trying to open them.

I am doing these tests, one book and one browser at a time, closing the Reader in FF before testing in Chromium, etc.

Thanks.

e-alfred commented 4 years ago

Some ebooks don't work well with this app, this is a problem with some of the libraries used by this app.

However, in Chromium, I can open the 1st book, and page through it without any problem ... however, books 2 and 3 do not open at all. I just get an eternal spinning wheel showing that it's trying to open them.

Do you see any error in the browser console?

spiraldancing commented 4 years ago

Hmm ... I'm actually seeing many errors in the Consoles of both browsers, different errors for different ebooks ... and yeah, some ebooks open and work in Chromium, some do not ... in FF, all books open, and no book with any defined Chapter divisions will page-advance forward across chapters (some will not even open Chapters from the eReader TOC slider).

I've tested about 8-9 books now, in both browsers. Seeing a lot of "null", "undefined", etc.

One specific book that does not open in Chromium has these console errors:

epub.min.js?v=1.4.2.0072:10 No Metadata Found EPUBJS.Parser.packageContents @ epub.min.js?v=1.4.2.0072:10 characterData (async) (anonymous) @ epub.min.js?v=1.4.2.0072:8 ja @ epub.min.js?v=1.4.2.0072:8 u @ epub.min.js?v=1.4.2.0072:8 r @ epub.min.js?v=1.4.2.0072:8 s @ epub.min.js?v=1.4.2.0072:8 (anonymous) @ epub.min.js?v=1.4.2.0072:8 j @ epub.min.js?v=1.4.2.0072:9 XMLHttpRequest.send (async) EPUBJS.core.request @ epub.min.js?v=1.4.2.0072:9 EPUBJS.Unarchiver.open @ epub.min.js?v=1.4.2.0072:11 EPUBJS.Book.unarchive @ epub.min.js?v=1.4.2.0072:8 EPUBJS.Book.open @ epub.min.js?v=1.4.2.0072:8 EPUBJS.Book @ epub.min.js?v=1.4.2.0072:8 EPUBJS.Reader @ reader.min.js?v=1.4.2.0072:1 a.ePubReader @ reader.min.js?v=1.4.2.0072:1 renderEpub @ ready.js?v=1.4.2.0072:134 document.onreadystatechange @ ready.js?v=1.4.2.0072:94 epub.min.js?v=1.4.2.0072:9 TypeError: Cannot read property 'manifest' of undefined at EPUBJS.Book.unpack (epub.min.js?v=1.4.2.0072:8) at epub.min.js?v=1.4.2.0072:8 at z (epub.min.js?v=1.4.2.0072:8) at A (epub.min.js?v=1.4.2.0072:8) at x (epub.min.js?v=1.4.2.0072:8) at MutationObserver.pa (epub.min.js?v=1.4.2.0072:8)

Here's another specific error-set from a (different) ebook opened in FF. Errors appear immediately on opening the book, with additional errors appearing on every page turn, whether successful or not:

Content Security Policy: The page’s settings blocked the loading of a resource at https://[baseURL]/index.php/apps/epubreader/WOOL_split_002.html (“base-uri”). epub.min.js:10:7662 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). injected.js:1:5301 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). inject.js:6:233702 Content Security Policy: The page’s settings blocked the loading of a resource at https://[baseURL]/index.php/apps/epubreader/WOOL_split_003.html (“base-uri”). epub.min.js:10:7662 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). injected.js:1:5301 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). inject.js:6:233702 Content Security Policy: The page’s settings blocked the loading of a resource at https://[baseURL]/index.php/apps/epubreader/WOOL_split_004.html (“base-uri”). epub.min.js:10:7662 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). injected.js:1:5301 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”).

The FireFox errors sound suspiciously like one or more of my add-ons are still interfering, despite being disabled, but I'd like to avoid completely uninstalling them (losing assorted config and history and such-like).