boox can't select text on calibre content server content

snmp · 03-02-2025, 06:59 AM

Hi,

I recently bought a boox device (Note Aur 4C) for reading ebooks.
I currently maintain my library managed by Calibre and exposed via the content server, so that I can resume books across my tablet, eink reader and PC.

On the boox I have tried chrome, default neo browser and brave, all are able to connect and load content from the server, but not allowing selection of text for annotation or for dictionary lookup.

On regular web pages this is not an issue.
Can anyone suggest what may be the issue and or if this is the same experience for your boox devices?

kovidgoyal · 03-02-2025, 08:13 AM

No idea, never laid my hands on a boox. Probably it does some hackery around touch events that breaks the selection code in the viewer, if I had to guess. The viewer JS manages selections itself unlike ordinary web pages where the browser manages selections.

nqk · 03-02-2025, 09:16 AM

Quote:

Originally Posted by kovidgoyal

No idea, never laid my hands on a boox. Probably it does some hackery around touch events that breaks the selection code in the viewer, if I had to guess. The viewer JS manages selections itself unlike ordinary web pages where the browser manages selections.

It happens with many devices, using Chrome or chromium-based browsers. On the same devices, I'm pretty sure Firefox would work.

On other devices, like Google Pixel 7 pro I'm using, the selection is not easy if using Chrome, but fast with Firefox and Waterfox.

This has been the case for rather long.

Sent from my Pixel 7 Pro using Tapatalk

kovidgoyal · 03-02-2025, 10:46 AM

Sadly I have never seen a device with chrome where it happens. So cant really help. Someone with access to such a device needs to figure out the issue and contribute a patch.

snmp · 03-03-2025, 05:41 AM

Quote:

Originally Posted by nqk

It happens with many devices, using Chrome or chromium-based browsers. On the same devices, I'm pretty sure Firefox would work.

On other devices, like Google Pixel 7 pro I'm using, the selection is not easy if using Chrome, but fast with Firefox and Waterfox.

This has been the case for rather long.

Sent from my Pixel 7 Pro using Tapatalk

Awesome, thanks a lot.... Firefox works perfectly fine.

03-02-2025, 06:59 AM	#1
snmp Junior Member Posts: 2 Karma: 10 Join Date: Mar 2025 Device: boox Air 4C	boox can't select text on calibre content server content Hi, I recently bought a boox device (Note Aur 4C) for reading ebooks. I currently maintain my library managed by Calibre and exposed via the content server, so that I can resume books across my tablet, eink reader and PC. On the boox I have tried chrome, default neo browser and brave, all are able to connect and load content from the server, but not allowing selection of text for annotation or for dictionary lookup. On regular web pages this is not an issue. Can anyone suggest what may be the issue and or if this is the same experience for your boox devices?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Calibre Content Server viewer] Vertical text not shown in Flow Mode	georgehuang	Calibre	4	05-27-2024 08:05 AM
Full Text Search Availability in Calibre Content Server	john2028	Server	5	01-22-2023 11:02 PM
Unable to select text when reading in iOS browsers through Content Server	georgehuang	Calibre	2	02-22-2021 02:13 AM
Best device for accessing Calibre as a content server only / Best way to add content	yelt	Calibre	1	10-01-2020 09:53 PM

03-02-2025, 08:13 AM	#2
kovidgoyal creator of calibre Posts: 45,339 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	No idea, never laid my hands on a boox. Probably it does some hackery around touch events that breaks the selection code in the viewer, if I had to guess. The viewer JS manages selections itself unlike ordinary web pages where the browser manages selections.

03-02-2025, 10:46 AM	#4
kovidgoyal creator of calibre Posts: 45,339 Karma: 27182818 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Sadly I have never seen a device with chrome where it happens. So cant really help. Someone with access to such a device needs to figure out the issue and contribute a patch.

Advert

Advert