Closed MysterieDev closed 2 years ago
i've also encountered multiple vue errors, this also happens generating an uuid for epub
thank you, I will try to fix them for the next release.
The first error looks like firefox, it should work in chrome correctly. It occures in firefox if the table of contents spans over two or several pages. Not sure why exactly it happens and not sure if the team from paged.js can help here. I will investigate.
@trendschau i've checked on my MacBook + Chrome (Chromium) and i've gotta admit, that i get a working result there (yay)
It kinda baffles me though. I've also tried it on Edge (Chromium) but that didn't seem to work either.
Yes, Edge does not work, they probably have a different implementation than chrome. Anyway, I am not sure if this errors are caused by page.js or if the script for the table of contents is wrong in some way. Have to investigate. Despite of that, I always use firefox, but only chrome for ebook-generation, because it delivers the most reliable results in this context.
I fixed the error with table of contents in Firefox, it was caused by css styling, I will publish it with the next release.
Hm, I fixed this bug but got other bugs depending on the content structure and not related to the table of contents script. I think Firefox is simply not reliable for paged.js, but I will open a ticket there if problem like this are known.
maybe (just an idea) you could make a javascript call to the user agent and display a disclaimer for browsers unlike chrome that the plugin does not guarantee to work on these browsers!
Good Idea and implemented in version 1.3.1 :)
I will open an issue to paged.js about the problems with firefox.
After updating i've encountered following error:
before updating ebooks, i made sure to copy 1.4.8s system folder to my installation, as the update-guide describes.
I think paged js has a problem with my content for some reason