Hyperlinks No Longer Working In TBird . . .
TBird Version: 140.7.1esr
Since yesterday I can no longer click through with hyperlinks inside an email message.
I don't understand this.
I have already tried all the troubleshooting items to no avail.
To my mind, a change was made to TBird's functionality and this is stopping the click-through to the default browser and the opening of the page linked.
Ausgewählte Lösung
Try this:
Open the TB profile:
- TB menu > Help > Troubleshooting information
- under the Application Basics section next to Profile Folder, click 'Open folder'
Close TB > rename the handlers.json file in your profile folder > restart TB
When you click a link now, you should be presented with a screen where you can choose which browser to use.
If that didn't work, try this:
Open the config editor:
- TB menu > Settings > General > scroll all the way down > click the 'Config editor' button
Search for and set these to true:
- network.protocol-handler.warn-external.http
- network.protocol-handler.warn-external.https
When you click a link now, you should be presented with a screen where you can choose which browser to use. Once done, reset the config options to false.
Diese Antwort im Kontext lesen 👍 1Alle Antworten (2)
Ausgewählte Lösung
Try this:
Open the TB profile:
- TB menu > Help > Troubleshooting information
- under the Application Basics section next to Profile Folder, click 'Open folder'
Close TB > rename the handlers.json file in your profile folder > restart TB
When you click a link now, you should be presented with a screen where you can choose which browser to use.
If that didn't work, try this:
Open the config editor:
- TB menu > Settings > General > scroll all the way down > click the 'Config editor' button
Search for and set these to true:
- network.protocol-handler.warn-external.http
- network.protocol-handler.warn-external.https
When you click a link now, you should be presented with a screen where you can choose which browser to use. Once done, reset the config options to false.
I had to clear the startup cache on re-entering TB after renaming the handlers.json file (handlers1.json?) but otherwise the first part of the procedure did the trick.
I also toggled the network.protocol-handler.warn-external.http & network.protocol-handler.warn-external.https booleans to true and it still works. So I'll leave them so for now.
Ace work, Ed.
Many thanks.
Sie müssen sich mit Ihrem Benutzerkonto anmelden, um auf Beiträge zu antworten. Bitte stellen Sie eine neue Frage, wenn Sie noch kein Benutzerkonto haben.