That’s the one I always use ![]()
I did set the delayTime to be 10000, I think I had problems otherwise with the script saving the image too early.
So maybe that’s just the missing thing in Bidoof’s script, a bit of a delay?
it is a timings issue, but i don’t really want to add a flat 1000ms delay just for windows users or something
the timings are caused by the fact that with the way how the script was written, with the script running at a flag called “document-end”, after everything else has loaded, the WebGL instance was already configured by the reader and then you can’t interact with it on Windows, while the timing of the implementation on Mac OS still allows for it to interact with it afterwards
so here’s an attempt of making it work with document-start instead, 2.53 released:
if it still somehow doesnt work, bwDebug.inspectCanvas() has even more debug information now
as a funny side note, my ebookjapan.yahoo.co.jp scraper just takes screenshots of the manga reading pages and then crops them because after a while of trying to force tainted canvas to give me the pixels I wanted I was like “you know what, i don’t have my whole life to debug this” ![]()
it does run much faster as a result xddd
but yeah, 2.53, give it up for 2.53, woo ![]()
I’m curious about Mokuro usage, as I’m planning to try moving from using Mokuro’s HTML files (and my wonderful scripts that interact with them) to .mokuro files in 2026.
Which Mokuro file do you use for reading your manga?
- I use the generated HTML file
- I use the generated .mokuro file
- I don’t use Mokuro
If you use the .mokuro file and use Mokuro Reader, where do you primarily use it?
- Using the official Mokuro Reader website
- Using Mokuro Reader installed on a different website
- Using my own local installation of Mokuro Reader
- I use a different reader that supports .mokuro files
- I don’t use .mokuro files
I’ve used your BookWalker-Screenshot-Simulator until two days ago. Now I suddenly get Always the Message “Downloading complete”. What could be the Problem?
I already tried different Manga and even deinstalling Chrome.
Have you checked if your scrolling direction is still Vertical?
Yes, it is. The Message came during a Download. And now it comes immediately.
I don’t know what happened, but at the moment it works again. I’m very confused. Maybe I did Mix Up vertikal and horizontal? But the Pages Had Always been Just a single one.
All’s well that ends well.
I can’t think of what would cause it to happen. If it were happening for only one single volume, the first step (which you probably tried) would be to reload the page and try again. But for it to happen across multiple volumes, I’m not sure.
I think it suddenly changed from vertical to horizontal during the Download and I didn’t realize it. It’s now working without Problems.
just wanted to report this appears to be working on my chrome windows (at least it’s about 30% through a scrape atm). Will report back
The main reason I stuck with the HTML files rather than Mokuro Reader was the lack of progress-tracking features I use (via a simple web page I wrote for the purpose).
What if I took the features I need and just added them to Mokuro Reader?
The initial result is my “progress tracker” branch of Mokuro Reader:
It’s still early development, and I’ll find issues to fix along the way, but I’m using it starting today, and plan to continue throughout 2026 (and beyond?)
Screenshot:
Annual Reading Goal — Set a number of manga volumes to read by the end of the current year and track progress.
It looks like I need to reach 0.3% of my goal today to keep on track for the year, and I’m sitting comfortably at 0.5%. (This close to 1% makes it feel like the year is almost over already.)
Currently lacking areas of this feature.
- No way to set different overarching goals, such as monthly or seasonal targets. It should be easy to implement.
- No way to view results from prior years. Maybe I’ll implement this after I’ve used it for a year?
Per-Volume Goal — Set a date to finish a volume by. Know at a glance how many pages per day to read from a volume to stay on track.
Currently lacking areas of this feature.
- Does not look at the number of pages read today (I think Mokuro Reader tracks this information) to say if a sufficient number of pages have already been read.
- Does not support milestone targets, such as “page # by date X; page # by date Y”, which can help to keep pace with book clubs.
Four Sort Modes:
- Last Read: Sorts by the time you last read each volume.
- Pages/Day: Sorts by pages per day reading needed to keep on target. Find which volumes you may be falling behind on.
- Fewest Pages: Sorts by fewest remaining pages in a volume. Useful to reduce how many volumes reading by focusing on those nearest completion.
- Deadline: Sorts by the nearest deadline. Ensure your numbers of looking good for the volumes you want to finish next.
will you be making any pull requests to the actual Mokuro Reader App?
i realized recently that with the Mokuro Web Reader you don’t see what’s the hard drive size of the manga, and it should be really easy to add this in this view for example:
but i’d probably have to pull request into mokuro web reader and im thinking if this is the right path to do things ![]()
At the moment, I’m not planning to. But I’m not committed in either direction.
The path to follow would be:
- Create a fork of Mokuro Reader on GitHub
- Create a branch. Name it as a “feature” or “enhancement” such as “enhancement/show-volume-file-size”
- Implement the feature
- Commit the feature to your GitHub fork
- Open a pull request
For something like that that some people might not be interested in, it might be good to have a configuration option to enable/disable it (disabled by default).
Famous last words
Hopefully the first of many!
I’ve gotten a much better idea of the development process for Mokuro Reader in the past couple of days.
The primary ZXY101/mokuro-reader doesn’t see much activity. Instead, development occurs over at Gnathonic/mokuro-reader (and then gets PR’d back to the original repo).
On Gnathonic’s repo, a release/[version] branch houses development and PR’s that will work their way into the primary release. I don’t yet know how I should properly “submit” a PR to the repo when I have one ready to go, but I’m on their Discord now, so I can easily ask when the time comes. If I did my first PR in the wrong place, it was probably not an issue this time around because a new release was just about to happen.
…which in this case was me writing up an implementation plan, having Claude Sonnet AI review the plan, then having Claude Sonnet AI implement it, then me reviewing the code, me resting the implementation, and me cleaning up the layout (including asking Google about Tailwind CSS classes).
All said, I only had to do the easy parts.
was tinkering a bit…finally figured out how to group them…at some point would be nice if/when better documentation comes out for mokuro reader but it seemed to work so I can finally organize my files a little bit more! Not quite folders in folders but finally a way to make this a bit neater
would be nice if the built in had a better sort and shelves for organizing … hint hint ![]()
also love that this should work on the boox!
One of the main issues in this area was that you have get into a situation where different volumes of the same series are not grouped together. (This is what my code submission resolves, merging duplicate series so all volumes are grouped together.)
But beyond that,
if you can write out what you imagine this to look like, that’d be one step closer to being able to put something together.
One thing I had a love hate with mokuro was doing all vol at once… I didn’t always want them all grouped because it wasn’t obvious how many vols there were (it’s much better now with the app)… so I would mokuro them separately… and thus creating a new series and moving them worked great!
But that was on a test mokuro thing on the desktop - need to clean up my real mokuro on the laptop, boox, tablet… not in a hurry… going to take some time…
Kind of like how BW has book shelves, which I don’t really use, but if it was files/folders…one bookshelf for say LNs related to 2026 bingo… then they all go in there instead of by title… as an option for customization…
And then for my 2026 manga card i have about 50 vol of manga I want to try to read (which isn’t probably realistic with the LNs)…but one bookshellf called 2026 manga then open that up and then each group of books by series in there…
basically allowing full control over the folders/files/organization, so you could potentially do anything you wanted to.
Realized also by being able to create my own series titles… can finally deal with the sorting mess…if you look at ttsu there are additional sorts other than A<>Z and smart… mokuro doesn’t have this level of sorting … could even allow tags per books (by user) so you could tag them and sort searches… so many possibilities …
of course the fact that we have a reader at all is pretty awesome!!! I have always liked how you have sorted your own bookshelves but not a programmer and setting up or running stuff isn’t my specialty… just want it to work … don’t want to waste my time trying to figure out fancy stuff when I just want to read.
could also take the BL/doujins put them away on their own bookshelf that looks innocuous and is hidden from the main scrolling screen





