Backspace Behaviour with Thai (could be other languages too)

I think this started happening in a recent version, because it’s infuriating typing in Thai now and I don’t remember ever being annoyed by this before now.

This doesn’t happen in different editors on the same operating systems.

Steps to reproduce

  1. Type a Thai word, like ที่
  2. Press backspace

Expected result

The first press of backspace should reduce ที่ to ที, then again, to ท, before deleting the entire character.

Actual result

Backspace deletes the entire character including all vowels and tone marks in one go, meaning you have to start the character again if you do a typo.

Environment

  • Operating system:
    Linux (Ubuntu Budgie 21.10), Windows 10, and Android
  • Debug info:
    SYSTEM INFO:
    Obsidian version: v0.13.19
    Installer version: v0.13.14
    Login status: not logged in
    Insider build toggle: off
    Live preview: on
    Legacy editor: off
    Base theme: dark
    Community theme: none
    Snippets enabled: 0
    Safe mode: on

RECOMMENDATIONS:
none


Additional information

Update:
My wife had Obsidian 1.0.4 on her iPhone, and it DIDN’T have this issue. She just updated to 1.0.5, and it DOES have the issue now. It has definitely been introduced in between these versions.

Also, the issue doesn’t happen on the title of a note, only in the note body.

More info: The issue doesn’t happen in the legacy editor

Does it happen here https://codemirror.net/6/?

Does it happen in source mode?

Does it happen here CodeMirror 6?

In that little box on the site? Yeah it does

Does it happen in source mode?

Yeah, in Source Mode and Live Preview mode.

Ok, so this is an upstream bug with the editor we use.
I am not familiar with how Thai language is supposed to work.

I suggest you open a bug report here: https://github.com/codemirror/codemirror.next/issues
and describe the problem that you see while using their demo page here https://codemirror.net/6/

Raised it here as requested:

It looks like I got a reply on the CodeMirror issue, and he closed it, but I’m not sure what he means - do you understand what he’s getting at?

He added a patch to fix the issue. We will apply the patch in one of the next releases.

Ah, glorious!!! What a great result. I guess this is case closed for now =)

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.