macOS deadkey composition

[lishid]

Seeing an inconsistent treatment for the backtick deadkey at the start of the line which is used to insert accented characters like à with some keyboard layouts. The same layout combo works fine on Windows.

To reproduce:

• macOS Chrome.
• Set the keyboard layout to English "U.S. International - PC".
• Try typing <backtick> + a.
• Observe that it only works sometimes.

[marijnh]

Also not happening with dead key layouts on Linux. Will try to test on macOS soon.

[marijnh]

I can't this to occur in Chrome 98 on macOS (tried about 20 times).

[lishid]

Maybe it's an OS issue? I'm testing on macOS Big Sur V11.6 Intel.
Just updated Chrome to 98 and can still repro exactly as the previous gif.

[marijnh]

Yes, I tested with an empty editor. Not entirely sure what the OS version was on the laptop, will check.

[marijnh]

Upgraded macOS from 10.something, where the problem didn't occur, to 12.2, where I still don't see it.

[WhiteNoiseDev]

Did you set the keyboard layout to "U.S. International - PC"?
Also is the OS doing the deadkey management or do you have keyboard that does it at a lower level?

[marijnh]

Yes, I set that keyboard and composed à chacters by typing a backtick and then a. I don't think my keyboard does something like this, no (plain old macbook laptop keyboard).

[lishid]

Here's the original bug report: https://forum.obsidian.md/t/extra-backtick-when-used-as-dead-key/30412
The report mentions macOS 12.1.
Oddly, it mentions the use of the option key "⌥`"

[lishid]

Update: I can also repro this in Safari on the website. macOS 11.6 as well.

[WhiteNoiseDev]

They mention the option key because in some layouts to get ` (and hence trigger the deadkey behavior) you need to physically press option+<another button> (e.g. option-9 in the Italian layout)

[habarahonaa]

https://forum.obsidian.md/t/extra-backtick-when-used-as-dead-key/30412

I can repro this on Chrome 97 macOS 12.2. Perhaps an issue with autocomplete is causing it?

[marijnh]

It looks like this may just be the closebrackets package interfering with the composition. Could you see if turning that off resolves the issue?

[lishid]

It does seem to work just fine without closebrackets.

[marijnh]

I've tagged @codemirror/closebrackets 0.19.1, which should help.