Add an option to hide or disable the reader setting toggles :maybe:

[thth]

I'm talking about these:

My reader settings get messed up sometimes, and I'm pretty sure it's because I accidentally click these toggles way too often.

I'd imagine for the majority of readers, these settings are something that they'd only want to change once, and would just function as a source of confusion and annoyance when exposed as a toggle outside of the settings menu, especially with how big the clickable area is.

Speaking of the clickable area, it extends the entire width of the div due to

width: 100%

from the

.w-100

class on the

reader-controls-mode-*

elements. At the very least, I'd recommend removing the

.w-100

classes on the toggles, which seems to remedy the huge clickable area problem without breaking anything.

 

[MavB_Ver]

You can hide it though, pretty easily by clicking the arrow at the right edge of the manga page, just a little bit beneath those toggles. Of course it will expand the pages' width, which would be kind of a problem if you chose the Fit width or No resize.

Edit: I just realised that you want to keep all the other options but those, which would be a fairly good point if I didn't also realise that all the troubles I had been having is incidentally double-clicked them, not mis-clicked them though. So yeah, from time to time, I need them to adjust my reader for specific pages/chapters too.

 

[Jumballi]

This is why I stick to the old reader. For as great as the current reader is, I personally just have too many issues with it.

 

[blackyawgdom]

also for those whos browser deletes cookies when closed, those settings reset.

 

[Teasday]

@thth To be frank I never thought anyone would have this specific issue, but I guess it's not impossible. Similarly I'm not sure why the three shortcuts would be a problem but accidentally clicking on the four other large buttons wouldn't be.

At any rate, the main reasons for why they're there is because they're essentially the most important settings in the reader and I wanted even new users to be immediately aware of them, and because they're useful as visual indicators of the status of the reader, especially because depending on the images and in case you've accidentally changed the settings (usually via keyboard) you might not be aware of the current settings and bringing up the menu to change them is a bit annoying. The fact that they double as shortcuts to manipulating their respective settings is a bonus.

That said, criticism duly noted. I'm not entirely sure how practical it would be, but I could see perhaps most if not all settings having a toggleable option for displaying them as shortcuts in the sidebar. I'll take it into consideration.

@blackyawgdom Technically localstorage rather than cookies, but regardless that's not something we're prepared to change. It's highly intentional that the reader settings are browser-specific so that people don't have to futz around with them every time they switch from desktop to mobile, for example. Also, if the reader settings were indeed saved on the server, anyone who keeps wiping their cookies is going to get constantly logged out anyway. People who do that already know what they're getting into, and I don't really feel like trying to fix their self-inflicted problems when it would be making things worse for the vast majority of users.

 

[thth]

@Teasday yeah, the issue could be too niche to warrant being a setting; I don't know how much this affects others and I'm only suggesting from the perspective of one biased end-user 🙂

In response to why these toggles are a problem for me and the 4 big buttons aren't: it's because of how visually indicative the buttons are of being clickable vs the toggles appearing as simple flat text. One possible UX suggestion to that would be something like adding a

:hover

rule to change the text color to increase the visibility of the text as being clickable.

That said though, I think you can agree that clicking here:

shouldn't be possible. (at least without something like the aforementioned :hover to indicate what the click would correspond to)
Do consider constraining the clickable area, such as by removing the

.w-100

class on those elements.