Not with the current system, the API is deliberately being designed to be non-specific to the user for performance purposes. Even if I had the data, I couldn't use the the same eye icon and would have to replace it with something text-based, because native HTML selects don't allow anything else. I'm deliberately using native selects because especially on mobile they're significantly superior to any custom implementations.@N0Mi0 posted:
Hm, I wonder if it'd be possible to add 'already read' sign in the chapter select menu inside the reader? Like in the usual chapter list.