And I, too, fell into the eInk mode by clicking on the scrollbar. Very odd design decisions there.
I couldn't figure out how to go "up" in pages. Pressing "Home" didn't do anything. So a lot of web browser / mouse / keyboard functionality is thrown out in that mode, which shouldn't be necessary to still be a good e-reader mode.
> Eink mode is not a closed-file format reader but rather a form of responsive web design (RWD) integrated into the website itself.
suggests to me that it's a display mode you have to enable in the CSS design of the site, like "print" layout. I.e. this particular version is not software you can use on any site, it has to be baked into the site.
Now the quest is to make this something that the user instead enables on her device for all sites.
If you're not already considering it, the Readability.js module might make this more straightforward:
<https://github.com/mozilla/readability>
(I think. I've looked into this but not applied it directly myself yet.)
These interruptions are especially annoying on e-ink.
You can tell Safari to use Reader Mode by default on all websites.
On iOS 18: Settings > Apps > Safari > Reader > All Websites.
On macOS 15: Safari > Settings… > Websites > Reader > When visiting other websites.
- Every website has the same accessible layout
- Blocks advertisements
- Blocks popups and auto playing videos
- Blocks cookie banners
- Blocks newsletter signup modals
- Blocks sticky headers and all distractions
- Auto dark/light mode on all websites
- Choose your preferred colour theme, font, font size and margins and it applies to all websites
- Images are presented neatly
- Inline videos are presented neatly
- Space bar to scroll down, shift+space bar to scroll up
- J/K to scroll between HTML elements (usually next paragraph)
- Can be disabled on a per-domain basis for when it's not suitable
The downsides:
- There are no downsides
If you combine these two projects, then you will have a great eInk experience for any kind of eInk device, and not much need for a browser plugin.
Granted, that is an example of a site and not a browser, but I would love it if a browser could magically transform websites to look like the Braille Institute's, where visual and cognitive accessibility are first-class citizens in the UX.
I really wish browsers were more modular - if the rendering engine and network fetching were easily separable - and you could insert your own steps into that pipeline, you could do all sorts of neat stuff. If I could insert some code of my own in between the fetch and the render, that would be ideal - strip out all ads and malware, optionally remove all scripts or css, run it through readability, etc...
Can’t that be done relatively easily with https://mitmproxy.org/?
Doubly relevant to eInk mode as soon be releasing a text-mode browser which has a verys imilar goal: make the web less noisy, and easier to focus on.
We try that by putting the web in the terminal. Technically it's similar to how the CloudFlare/S2 remote browser works in that we take rendering instructions from the remote browser and display in your terminal, except instead of rendering everything from the browser engine, we only render the post-layout text boxes! To do this you need to apply a secondary layout pass account for overlaps due to monospace font sizes, and scaling to terminal dimensions.
That's why I'm thinking that people interested in eInk mode might care about this browser too, a quick demo of which is here: https://youtu.be/Xmt6j-nfc7E
If you'd like to be among the first to test it out when ready please add your name / email to this list: https://tally.so/r/wbzYzo
I hope they do not enter the eink device market. Eink in general is unfortunately already suffering from the stranglehold of one giant which has locked innovation away due to its proprietary implementations. Having two will not make the situation better, only worse.
One of Einkbro's highly underappreciated features is "save page as ePub". This provides the "web as ebook" experience you're looking for.
But it gets better: You can save multiple pages to a single ePub, where the additional pages are appended to the end of the document. This provides a book (or multiple books) which can follow a theme: a set of pages on a topic, a time-oriented collection of pages, etc.
The UI/UX isn't as seamless as reading online, but the end result is really good.
Note that an ePub document is a compressed archive of HTML documents. You can pull apart the ePub to edit it: re-order contents, re-title them, edit the underlying documents themselves, etc., using shell tools. On an Android device itself directly if you've installed Termux. A bluetooth keyboard helps immensely here.
I've been raving about this feature for years now, see: <https://toot.cat/@dredmorbius/107958709435468728>.
Essentially, imagine Reader Mode, but all the time.
But this is... something else? I tried scrolling to the bottom and as soon as I click on the scroll bar, I get a pop-up showing a bunch of gestures and can no longer scroll. Pressing the back button does nothing. Closing the tab asks me if I want to discard my unsaved changes?!
So I'm guessing this is some CSS/JS to make a regular site _behave_ something like an e-reader? Which may be fine as far as it goes, I just don't think it's a good idea to hijack the scroll