Highlights in reader, when nested, overwrite one another

Bug #1991597 reported by Rainshoots
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calibre
Fix Released
Undecided
Unassigned

Bug Description

When annotations are nested in Reader, the outer-most highlight overwrite everything in between and there is no easy way to recover notes that's been lost.

Nested highlights can happen accidentally due to cursor orientation.

Example: [1[2][3]]

Notes within [2] and [3] would be gone when [1] is applied.

-----

Calibre version: 5.37
OS: Ubuntu 22.04, iOS 16.0.2 (Calibre Server)

Revision history for this message
Kovid Goyal (kovid) wrote :

I dont see what calibre can do here. It cannot know that the user didnt mean
to overwrite the existing highlights. And a confirmation popup is
redundant since the new highlight only takes effect if explicitly
applied.

At best it could automatically append notes form overwritten highlights
to the new highlight, but I can see this being fairly
annoying/unexpected.

Changed in calibre:
status: New → Invalid
Revision history for this message
Rainshoots (astyh83) wrote :

Can an undo function be implemented so that obliterated notes can be recovered?

OR

Fix the highlight function so that nested highlights don't happen accidentally: Eg. Warn the user before a nested highlight takes place.

Revision history for this message
Rainshoots (astyh83) wrote :

In my case, the front cursor flew off the screen, spanning entire chapters when I proceeded with the highlight, not knowing what is about to happen; an entire set of notes has been lost.

Revision history for this message
Kovid Goyal (kovid) wrote :

Ah, you are on iOS. No wonder. Well, I will add a confirmation popup for iOS when a highlight contains existing highlights.

Revision history for this message
Kovid Goyal (kovid) wrote : Fixed in master

Fixed in branch master. The fix will be in the next release. calibre is usually released every alternate Friday.

 status fixreleased

Changed in calibre:
status: Invalid → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.