Jump to content
fncll

Firefox frontmost window triggers large text .. with some letters

Recommended Posts

I have a strange problem. If Firefox is the active window when I invoke Alfred, then entering the letter p and waiting a fraction of a second causes the large text feature to activate and then get dismissed (along with Alfred). This happens with no other apps running, it happens consistently with Firefox in the foreground, and it happens even with Firefox in "safe mode" with all add-ons, etc. disabled.

 

I am running OS X Mojave 10.14.3, Alfred v3.8 [959] and Firefox 65.0  

 

Any thoughts on how I can troubleshoot this?

Share this post


Link to post
22 hours ago, fncll said:

Any thoughts on how I can troubleshoot this?

 

First of all, do you have any other applications that modify keyboard or focus behaviour (Karabiner etc.)?

Share this post


Link to post

@fncll It's the first time I hear of this kind of issue; It looks like something must be dispatching a Cmd + L key combo (the Large Type combo) or another key combo you may have set for Large Type in workflows.

 

  • Are you saying that the issue specifically only occurs when you type "p", don't press return and wait?
  • Or does it happen when you type any text and wait with Firefox in the foreground?
  • Does it occur with ANY other apps in the foreground?

If you think you've disabled all third-party apps on your Mac that could be interfering, but still see it happening, try creating a secondary user account on your Mac, and testing the same thing there with absolutely nothing else other than Alfred and Firefox running. 

 

The more troubleshooting you can do to find out exactly when it does or doesn't happen, the more likely we can help you. This isn't a known issue or something anyone else has reported, so you'll need to do a bit of digging :)

 

Cheers,
Vero

 

 

Share this post


Link to post

I'll try the 2nd user account test. In the meantime:

 

  • It only happens when Firefox is the active window when I invoke Alfred
  • It only happens when certain text is entered, particularly the letter p or, if type fast enough to get more characters in before large text is triggered, any word starting with p

 

Even stranger, once it happens, the next time I invoke alfred, it seems that *any* text I enter has this happen ... and then the next time I invoke Alfred, all is fine (except the dreaded letter p :)

Share this post


Link to post

Also, even stranger, if I use Karabiner Events viewer, it shows no events differently when this happens with Firefox as the frontmost app than it does when things are normal with any other app frontmost...so whatever is triggering it is not being seen as a keystroke event :)

Share this post


Link to post

I figured out the problem: it is a bug/problem with this Pinboard workflow: http://www.packal.org/workflow/pinboard

 

The description says it works with Firefox but the README, and an issue report on GitHub, indicates a problem with these symptoms...though it appears there should be a workaround, that doesn't seem to be the case currently.

 

All that said, it would be nice to be able to disable Large Text so this keyboard shortcut wasn't monopolized (or have an option to choose another key combo in Alfred)...

Share this post


Link to post

@fncll You can pop a post in the thread for that workflow with your findings:

 

Either the workflow creator, or fellow users of Pinboard may be able to help you resolve this :)

 

Cheers,
Vero

Share this post


Link to post
7 hours ago, fncll said:

I figured out the problem: it is a bug/problem with this Pinboard workflow: http://www.packal.org/workflow/pinboard

 

The description says it works with Firefox but the README, and an issue report on GitHub, indicates a problem with these symptoms...though it appears there should be a workaround, that doesn't seem to be the case currently.

 

You’ve stumbled into why most people that build browser automation tools and Workflows do not include Firefox (and also why some people avoid Firefox completely): lack of AppleScript support.

 

Presumably, what that Workflow is doing to support Firefox is automating keystrokes, in this case ⌘L to select the address bar followed by ⌘C to copy its contents. This (and any method that relies on automating key presses) is hacky and should be avoided, though if you really want to keep Firefox, you don’t have much choice.

 

I recommend you go to Mozilla’s bug tracker and be one more voice asking for AppleScript support. Though some of those requests have been open for 17 years, so I wouldn’t be hopeful.

Share this post


Link to post
21 hours ago, vitor said:

You’ve stumbled into why most people that build browser automation tools and Workflows do not include Firefox (and also why some people avoid Firefox completely): lack of AppleScript support.

 

This is really starting to bother me now that Google has gone full-on evil with Chrome and Apple is gutting extension functionality.

 

I can't conceive why the divvies at Mozilla decided to remove AppleScript support instead of improving it.

Share this post


Link to post
On 2/13/2019 at 9:52 PM, deanishe said:

This is really starting to bother me now that Google has gone full-on evil with Chrome and Apple is gutting extension functionality.

 

Same. There’s no browser today that fits my needs:

  • Safari’s content blocking is laughable. The 50k rule limit is less than a third of my uBlock rules. Plus, there’s really no good content blocker I’d trust to be kept up-to-date — the only decent one, 1Blocker X, exists only on iOS and there seem to be no plans to update it to macOS. Plus, Safari has no fine grained control to only allow JavaScript on certain websites. In sum, Apple has a good stance on privacy but their actions are lacklustre.
  • Ungoogled Chromium is a nice effort, but since they are removing code from another project, I don’t trust them to somehow not remove something they should, or not be behind on security features.
  • Opera and Vivaldi drink from the same water as Chrome, and I worry abou their affiliations. In this day and age, I’d rather not trust a closed-source web browser.
  • Brave also drinks from the same water as Chrome. They claim they don’t have to follow their bad practices, but the tune may change when they start to have to maintain their own browser engine fork due to the differences.
  • A bunch of other web browsers that neither support AppleScript nor have enough users/scrutiny for me to trust them.
  • Firefox has no AppleScript support and its performance on macOS is atrocious. I can get past the latter, but not the former.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×