FAKKU Reader Help, Feedback and Bug Report Thread

What OS and Chrome version are you on? I had issues like this earlier in the development process but they should have been weeded out properly a good while back.

Also, if you go into F11 fullscreen mode, the fullscreen button in the reader gets disabled on purpose, as you can't exit F11 fullscreen without pressing F11 again. This is the case with all browsers. (Side note: F11 fullscreen mode is very evil in the way it co-operates - or rather, how it doesn't - with the HTML5 Fullscreen API. It has been a source of some great frustration on my end.)



I'll likely an option to turn scroll wheel page changing off, but it will be defaulted to on to match CDisplay's scroll wheel behavior.



These are all good ideas to keep in mind whenever I actually get around to working on a double-page mode. Thanks.



Some sort of "resume reading" functionality would definitely be a good idea. Though we'll need to come up with a way to make it as unintrusive as possible.



It's based on page edges and the current fitting. So if you have background visible on left and right, the color will be based on the left and right edges of the page. Same for top and bottom if background visible there, and it uses all edges in case there's background visible on all sides.



Page reloading would likely be quite annoying, but maybe some sort of notification to show that the arrow button functionality has been swapped would be a good idea.

---

Also, to anyone having issues with book loading failing, you could try clearing your cache / hard refreshing the reader and see if that solves the problems.

This might fall in line with the bookmark suggestion other users have said, but having the ability to favorite individual chapters, such as if I wanted to only favorite the chapter "I Lock you" instead of the whole book would be a great feature for the future.
Don't know how intrusive and difficult this would be though and it does sound similar to the bookmark feature, just tossing in my 50 cents.

I also have the issue with the "Failed to load book" promt, which links back to the Renai Sample overview page.

Clicking on a download link proceeds with a straight jump to the main page.

That means I cannot read or download the book, actually.

I'm using Firefox 32.0.3, Windows 7 x64

Edit: Also tried Opera 12.17, same results.

Edit: Didn't look at the comments - seems to be heavy traffic, eh? ^^

I am on Windows Vista Home Premium 32bit and Chrome Version 37.0.2062.124 m

Added a note to the OP about "Failed to load book" errors, which I might as well post as a new reply too:

Are you getting a "Failed to load book" error? This is unfortunately not something that I can fix myself (I'm a front-end developer and it's a back-end issue), but the person who can (Jacob) is aware of it and is working on it. In the meantime, you could try and see if it works in a different browser - Chrome seems to have the best success rate.

The book keeps failing on me :( And I've tried everything, clearing cache, changing to chrome, and nothing. Downloads redirect me to the front page. I'm glad Jacob is working on it, I hope this can be fixed, in the meantime I guess I'll have to wait T.T

Thanks, confirmed as working. Might still want to do something about the name, though. While "[Homunculus]" might work for now, it would still be nice to have the file name include the book name as well, especially considering more books coming in the future. ;)

the red bar at the top and bottom wont go away

Not even when you press Enter? Or when you move your mouse around in the middle of the screen?

yep, i tried moving my mouse to the center, pressed enter, reloaded too, but they just stay there.

What device, operating system and browser are you using? Are they up to date?

I don't seem to have an issue with the layout on my computer (using google chrome).
Edit: just recently tried to read it and I get the "failed" on my computer now lol

Did have some issues with it on my iphone4s (updated to the new ios 8.0.2)
- sometimes the red bars lag/won't go away
- buttons to increase size or decrease size of pages don't work
- slow or doesn't load to the next page
- if you try to reload it you get a "failed" icon at the top

im on my laptop, running on the most recent version of windows, with chrome- its also up to date.

The same thing happens on android (cm10, most recent chrome build). The scaling issue is also present in a different manner on my desktop (win7, most recent chrome) where the scaling will change the size, but will not change it properly or center the page (ie "fit to height" results in this: http://puu.sh/bPBBi.jpg). In regard to the lack of zoom functionality on mobile, it's technically readable, but not being able to zoom in on things makes it much more difficult to actually use the new UI. Overall, the new interface looks great - visually it's gorgeous and seems much more polished, even if some elements could use minor adjustments. From a usability standpoint, however, it definitely needs some work. It may not be perfect yet, but it definitely has potential.

Side note: have you guys considered allowing users to switch between the new interface and the old, basic one?

Unfortunately, manipulating scrolling manually would disable any smooth scrolling a browser might do by itself (while I don't use it myself, I have to say that IE11 has real sexy smooth scrolling and I'd hate to have it disabled). Then again, we do this for keyboard scrolling already, so it could be considered. Maybe it could have a default option that uses a browser's own scrolling.

And for what it's worth, I'm fairly sure it's only Firefox that's scrolling very slowly for some reason.



The reason the page scaling options "don't work" is because the reader currently has forced "fit to width if overwidth" enabled, as mentioned in the opening post. This will be made into its own option soon enough. This way you should be able to use the X% Original Size scaling options (which will also be made more comprehensive in the future). Native zooming is unlikely to happen since it would scale the UI as well. If only you could set elements as "non-scaling" for web-apps, things would be so much better...



The new reader is intended to replace the old one completely, so that will likely not be a thing when it gets rolled out site-wide.

As for your other desktop issue, that does seem like a bug, but I can't reproduce it here. The only time I've seen weird scaling like that is when the reader loads with the browser minimized / in the background in Firefox... Out of interest, are you running Windows with a higher-than-normal UI scaling?



What Android version are you running? Can you give Chrome for Android a spin?