3
  1. Focus on any input field on any website (e.g. the search bar on orionfeedback.org)
  2. Switch to Japanese input method. Use "Japanese - Romaji". (How to add the input method in macOS system settings: https://support.apple.com/guide/japanese-input-method/jpim10267/6.3/mac/14.0 )
  3. Type anything in the input field. Try "konnichiwa". What you type won't be displayed in the input field, which is probably related with the problem. But if you press backspace a few times now, the browser will crash.

Expected behavior:
What you typed in the input field with Japanese input method should be displayed, and pressing backspace after typing won't crash the browser.

0.99.127.3.1-rc (WebKit 619.1.11.111.2), macOS 14.5(23F79)

Sonoma (14)

    14 days later

    stonekyx I see in the screen recording when you trigger the keyboard shortcut to switch input modes the only input mode is Hiragana. How are you able to get that state with "Japanese -Romaji"? I can only de-select Katakana, the Romaji checkbox is disabled unless I add another Roman letter Input Source

    Or

      astruckm Have you tried pressing Ctrl-Shift-Space? Or if it doesn't work, please check System Settings -> Keyboard -> Keyboard Shortcuts -> Input Sources, and see what's the shortcut for "select previous input source". Once you trigger that shortcut, it should rotate through all your available input sources including Japanese - Romaji.

      Or do you see a input source selection button on the menu bar? It should appear when you have multiple input sources. If it doesn't, check if the option is checked in the "All Input Sources" tab in your screenshot.

      In my screen recording, I actually switched to Japanese - Romaji directly (the blue "あ" icon means it's Romaji input, not Hiragana input. The latter would show "かな" instead.) That's because I have a Japanese keyboard, which has a special key made specifically for switching to your default Japanese input method.

        stonekyx Thanks for the breakdown. I'm able to now consistently reproduce the issue, and we're able to diagnose and fix (looks to be WebKit-related)

        a month later
        No one is typing