search

i3roly / firefox-dynasty

haters puttin' a wrap on us, callin' it a legacy, we keep showin' what the fuss, call it a dynasty
Other
3 stars 1 forks source link

OS X's native "text replacement" feature does not work in Firefox #10

Open Wowfunhappy opened 1 month ago

Wowfunhappy commented 1 month ago

OS X has a wonderful, built-in feature for system-wide text replacement, as documented here: https://www.theatlantic.com/technology/archive/2014/05/the-best-way-to-type-__/371351/

For a (very) long time, this wasn't supported in Firefox. However, it looks like this was finally fixed last month, in Firefox 130: https://bugzilla.mozilla.org/show_bug.cgi?id=1149826

However, text replacement appears to still not work in Firefox Dynasty, at least on OS X 10.9. I wonder if this could be fixed?

i3roly commented 2 weeks ago

i haven't touched anything related to this.

read those commits closer and try enabling the flagS? they seem to be DISABLED by default.

maybe i'll get around to this otherwise, but i didn't touch anything here so i can't say whether this will be added or not.

sorry

Wowfunhappy commented 2 weeks ago

Wait, okay, I'd tried the flag before (setting widget.macos.automatic.text_replacement to true in about:config), and I was about to say it doesn't work, but I tried it again and it does work, except it's very slow. That is, if I type "omw" and keep going to the next word at my normal typing speed, the replacement doesn't happen. If I type "omw" and wait for a bit before I continue, the replacement shows up.

I need an opportunity to test standard Firefox on modern macOS to see if it's faster there. If it's not, this may be an upstream bug (in which case, I just really hope it doesn't take Mozilla another seven years to fix).

i3roly commented 2 weeks ago

don’t get your hopes up.

looking at the central branch, it feels like they’re deliberately trying to break this build.

there is something on central that is causing older OSes to crash on run. this doesn’t affect any posted build right now, but i don’t think they want sidebar going live on older OSes because they just don’t like me. well, some of them don’t.

thankfully at this time the beta and release branches are still going strong, even with the latest commits. but bisecting the changes between beta and central will be annoying.

they should be more supportive. they’ve really clammed up in their chat channels now, too.

i suspect someone from ‘above’ has threatened them or something.

On Oct 3, 2024, at 8:03 AM, Jonathan @.***> wrote:

Wait, okay, I'd tried the flag before (setting widget.macos.automatic.text_replacement to true in about:config), and I was about to say it doesn't work, but I tried it again and it does work, except it's very slow. That is, if I type "omw" and keep going to the next word at my normal typing speed, the replacement doesn't happen. If I type "omw" and wait for a bit before I continue, the replacement shows up.

I need an opportunity to test standard Firefox on modern macOS to see if it's faster there. If it's not, this may be an upstream bug (in which case, I just really hope it doesn't take Mozilla another seven years to fix).

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

MacBiter commented 1 week ago

I wonder if it's worth using a system wide text expander such as TypeIt4Me or TextExpander? I've used TI4M for 30 years so it's a no brainer for me.