Thank you very much for your suggestions. These are very constructive and I will try to implement them in the future. Could you tell me which browser and environment you’re using? I’m trying to figure out why it loads slowly.

Hi! This was on a Boox Tab X, trying on Firefox and Chrome. I will make some more tests and get back to you.

Thank you. I really appreciate your help. By the way, the v0.0.2 update has been released. I added a function to remove 80 ~ 90 % of the Ads on any webpages to make the layout cleaner. And some desktop users want dark theme, so I added a switch to toggle between dark and light theme. As for UI improvement, I'll do it in the later updates.

Thank you! My next step is to submit the extension to the Edge and Safari platforms. I expect the Safari review process to be more rigorous, so I will address some existing issues before submitting.

I think Kindle's experimental browser does not support javaScript so that's the reason why there's no eink icon. I do hope I can use Eink mode on my Kindle too.

It has limited JavaScript support according to this: https://imgur.com/a/Ig8MyyH Should be enough to implement the claimed features at least.

Actually, EinkBro's Reader mode is using Mozilla's readability.js. I've actually been using EinkBro for over four years. One of the main reasons I want to develop Eink Mode is to achieve true pagination, where text and images aren't cut off at the edge of the screen. EinkBro's approach involves scrolling a fixed distance by tapping page turn zones on the screen (just like pressing the space bar when using a desktop) , and it removes the scrolling animation using "jumping" by a 'scrollHeight' amount. However, this still has the issue of potential content cutoff.

Eink Mode + Ebook Mode = A fully functional web browser for Kindles, which is the most popular eInk device by a large margin.

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.

This sounds great! Maybe we can cooperate and try to make it happen.

That's great. A browser extension is a more proactive approach for E Ink users.

I'm glad to hear that. Thank you.

Thank you for your appreciation.

I've tried Reader Mode, but Safari's Reader Mode doesn't properly display JavaScript elements, such as my footNote popups, and some YouTube videos also fail to load correctly. Additionally, embedded Google Maps within this article don't appear accurately, and many website layouts get distorted. Furthermore, current Reader Modes on major browsers predominantly rely on scrolling, which isn't ideal for E Ink. These shortcomings are pain for E Ink users and this is why I'm advocating for this alternative mode.

I completely agree. When it comes to eInk, then classic reader mode scrolling is an inconvenience. But compared to normal browsing, it is great. As for distorting website layouts, that is usually a bonus. Reader mode + standardized website navigation layout would be the golden solution.

Thank you for your feedback. I do plan to turn this into a browser plugin.

That would be absolutely awesome.

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.)

Thank you for your suggestion. I may look into the implementation of how it fetches the main article of the document.

Thank you for bringing this issue to my attention. I will try to modify it to automatically detect if the user has used highlighting or handwriting features, and only then will this prompt appear.