Site specific override
As far as I know, using a site specific user agent override was a feature dropped from Firefox and therefore TFF - is it possible to bring it back without causing problems?
I found it was useful to adjust the config file to use different user agents on a site by site basis.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Cameron Kaiser on 12 Nov, 2019 01:47 AM
It looks like this was pulled in https://bugzilla.mozilla.org/show_bug.cgi?id=896114
It should be possible to revert that, but the reason they took it out was a non-trivial 9% performance hit, so this isn't a slam-dunk. I might see if a master pref can be used to control it such that if the pref isn't set, the browser doesn't initialize it.
2 Posted by Wayne Sadler on 12 Nov, 2019 09:14 AM
Thanks - appreciate that. If it really does drag browser performance down 9% that's an unacceptable negative on PPC Macs which need every CPU cycle they can muster.
Support Staff 3 Posted by Cameron Kaiser on 22 Nov, 2019 03:12 AM
A first pass is in the FPR17 beta, which appears to basically work with my simple testing. I have decided I don't want to officially support it, but I'll leave it there for people who understand its limitations and risks. See
https://tenfourfox.blogspot.com/2019/11/tenfourfox-feature-parity-r...
4 Posted by Wayne Sadler on 22 Nov, 2019 09:16 AM
That's great - thank you. I'll download the beta and test asap. Cheers.
5 Posted by Widar8472 on 04 Dec, 2019 08:50 AM
The problem since FPR17 is, that I can't configure extensions like NoScript or Ghostery. There is no configuation button in extensions menu like before. Any suggestions?
Support Staff 6 Posted by Cameron Kaiser on 04 Dec, 2019 04:47 PM
Please don't tag on to existing tickets if you have a new concern -- please open a new one.
In response to your query, I didn't make any changes to add-on compatibility in FPR17. If you like, please open a new ticket with what version of the add-ons you are using and where you got them from. A screenshot showing exactly what you're referring to that's missing would be helpful.
Cameron Kaiser closed this discussion on 04 Dec, 2019 04:47 PM.