Firefox Assistant

[Alfred0 0]

Ah, would it be possible to turn it on conditionally based on the installed firefox version?

 

Or perhaps make it a workflow config option that’s disabled by default?

Edited January 24 by Alfred0

[deanishe 1,405]

2 hours ago, Alfred0 said:

Ah, would it be possible to turn it on conditionally based on the installed firefox version?

 

I don't think so. It's a syntax error, which typically means the script will fail to parse, never mind run.

 

I think if I mark the new version of the extension as incompatible with older versions of Firefox, it should be okay. People running older versions of Firefox shouldn't get the update, and if they want to install the extension, they can grab an older version of it.

[Alfred0 0]

15 hours ago, deanishe said:

 

I don't think so. It's a syntax error, which typically means the script will fail to parse, never mind run.

 

I think if I mark the new version of the extension as incompatible with older versions of Firefox, it should be okay. People running older versions of Firefox shouldn't get the update, and if they want to install the extension, they can grab an older version of it.

 

Great news! I'll keep an eye out for the new release.

[deanishe 1,405]

Just now, Alfred0 said:

Great news! I'll keep an eye out for the new release.

 

It doesn't work properly. Looks like the author of the PR didn't test it. Not particularly surprising, seeing as they didn't even bother to check which versions of Firefox the workflow supports.

[Signynt 1]

For some reason when I try to select a tab from the search it takes forever to switch to it. It takes upwards of a minute to suddenly switch to the selected tab.

[deanishe 1,405]

47 minutes ago, Signynt said:

For some reason when I try to select a tab from the search it takes forever to switch to it. It takes upwards of a minute to suddenly switch to the selected tab.

See previous page. Unless someone who’s affected by the issue can figure it out, you’re going to have to wait (a possibly long time) till I get an M1 Mac and/or upgrade to Big Sur.

[nchicong 0]

Hi @deanishe

Thanks for the great workflow.

 

I'm looking for a way to 'Activate Tab' by tab index instead of tab ID.

The idea is like

`./alfred-firefox -tabIndex 2 -action "Activate Tab" tab`

 

I looked at the workflow code and it looks like it's only using tab ID.

I would appreciate it if you have any suggestion.

[deanishe 1,405]

The workflow doesn't expose (or use) window or tab indices. I deliberately avoided that because they can change very quickly.

 

What are you trying to do?

[nchicong 0]

@deanishe

I work with a lot of tabs and on Chrome I have a workflow to map Ctrl + number to jump to the tabs.

Ctrl + [0 to 9] to jump from tab 0 to 9

Ctrl + [q to p] to jump from tab 10 to 19

Ctrl + [a to ;] to jump from tab 20 to 29

 

I customized the workflow named Chrome Control

```

x={query}
y=$(($x - 1))
./chrome.js focus 0,$y

```

 

I would like to do the same on Firefox. Some times during research, on Firefox with Vertical Tabs, I use up to 40 tabs.

[deanishe 1,405]

Right, I've got you. I can see how that would be very useful.

[vitor 879]

Without a way to specify the keyboard layout, the feature as explained could cause some problems.

 

Even in places where QWERTY is used, the a to ; might not work. It wouldn’t in Portugal, where ; is to the right of m (they key next to l is ç).

[nchicong 0]

@vitor

I don't think the keyboard layout is a matter. For me, I simply hard code the key as each input. I attached my screenshot of my setup.

 

Another required component is to combine this with browser extensions like

https://addons.mozilla.org/vi/firefox/addon/tab_numbers/

https://chrome.google.com/webstore/detail/tab-number/hgncmdcajoembohielokebjhljfajddj

Edited February 24 by nchicong