Text replacements / expansions doesn't work on MacOS

[Magistern]

on iOS and macOS there is a feature called Text replacements. If I type :) it could be replaced with 😊, or if I typen@ it could expand to name@domain.com. It works in all applications, native or otherwise except Chrome and Electron apps (except Typora actually where it does work).

Would it be possible to bypass what seems to be a chromium "bug" and still make it possible in Electron? I believe the native property is automaticTextReplacementEnabled on the NSTextView class.

[welcome]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

To help make it easier for us to investigate your issue, please follow the contributing guidelines.

[MarshallOfSound]

This is implemented in userland.

https://www.npmjs.com/package/electron-text-substitutions

[socksy]

@MarshallOfSound what's the reasoning behind that? (Other than FOSS developer scratching their itch in user land).

Surely a field on a NSTextView is preferable to a library that is reinventing the system by looking into the system preferences, finding the list of substitutions, and doing the substitution in JS?

Is it because of the underlying complexity of Chromium?

[MarshallOfSound]

@socksy Chromium doesn't use NSTextViews for it's text input. This is a longstanding issue in Chromium which I've heard recently is going to get some traction but we're entirely dependent on this implementation.

https://bugs.chromium.org/p/chromium/issues/detail?id=42434

[socksy]

Thanks for the clarification!

[javan]

Chrome now has support for native text substitutions. Not sure if it was a Chrome or Chromium change, but maybe it's something Electron could pull in?

[javan]

This is a longstanding issue in Chromium which I've heard recently is going to get some traction but we're entirely dependent on this implementation.

https://bugs.chromium.org/p/chromium/issues/detail?id=42434

@MarshallOfSound, it looks like that ^ issue has been resolved and Chromium seems to support text substitutions on macOS now (see my comment above). Could this issue be re-opened as a feature request? Or, would you like me to open a new one?

[mitchchn]

Would also like to see this added as a menu role, it seems the support is there in Chromium (and the substitutions do work even though the menu isn't present).