[Bug Report] Cursor jumps behind bold text when deleting trailing space after bolded colon in list items

Desktop editors
,
1

I posted this at helpdesk, but was told to move it here!

Product / Version:

  • ONLYOFFICE Docs Desktop
  • Version: 9.2
  • Platform: Windows 11

Steps to reproduce:

  1. Create a list item (bullet or numbered).
  2. Paste a text with part of it bold and a leading colon followed by normal text and a leading space.
  3. Switch to another part in the document, then go to the end of the line.
  4. Delete the trailing space at the end.

Expected result:

  • The cursor should remain at the end of the line, after the normal text, delete the space and be ready to continue typing.

Actual result:

  • The cursor jumps behind the bolded colon unexpectedly.
  • Happens intermittently, not every time.

This also happens if you copy/paste text from one part to another inside the same document and copied bold text. If you try to edit the copied text somewhere, it jumps right behind the bold text.
This only happens once per section.

Further sometimes it copies an additional space right to the end, which has some strange behaviour.

2

Hello @Torsten

I was unable to reproduce the issue, but most certainly I misunderstand the wording you use. Second step of the provided scenario seems to be the key, but it is not clear whether there should be 3 items in the list or just 1 with some fancy content.

Can you record a video demo with the issue for better understanding?

3

Reproduce:

  • Type "Test: The front is bold " [trailing space]
  • Type “Pos1” Key (jumps to the start of line)
  • Keep pressed STRG+Shift and press twice ArrowKeyRight (marks Test: including the space)
  • Press STRG-B
  • Press “End” key (jumps to the end of line)
  • Press “backspace” (should delete the last charakter (space)

==> But it jumps richt after the bold space behind "Test: "

You can type it or copy the text from here, same result.
And it only happens once. Jumping back to the end will work from now on for this line.
image

4

Thanks. At first I was confused by the namings, but then I managed to reproduce the behavior. I have forwarded this scenario to QA team for analysis. Please await my feedback.

1 Like
6

QA has confirmed the bug, it is registered as number 66602. Thanks for reporting this issue.

1 Like