Why does Theme and Font Size add on opens in new tab randomly?
Without warning or an action on my part the theme and font size add on opens in a new tab. To get rid of it I have top close the tab. How do I prevent this?
Windows 10 build 1607 FF build 14.0.1
Thank you.
Giải pháp được chọn
In case of problems with updating then best is to go to the official Mozilla website and download the latest version there.
You can find the full version of the current Firefox release (50.1.0) in all languages and all operating systems here:
Version 50.1.0, first offered to Release channel users on December 13, 2016Đọc câu trả lời này trong ngữ cảnh 👍 0
Tất cả các câu trả lời (5)
That is how the developer of this extension deals with updates. When one of his extensions updates then you (suddenly) see the home page of this add-on opening. I don't know of a way to prevent this.
There are other things that need attention.
The System Details list next to the question shows that you run an older Firefox 41 version that is no longer supported with security updates.
- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0
Always update Firefox and Add-ons to the latest versions to get all security fixes.
Please update to the current Firefox 50.1.0 release.
- Help -> About Firefox
Thank you very much! That cleared it up.
You mentioned my Firefox was out of date and sent me a link to correct it. I went to Help/About and checked for updates. Here is what it reported: I have tried to add a screen shot of the window but it doesn't seem to be going well. I showed version 41.0.1 and said it was up to date.
Is that correct. If not how do I update?
Thanks again.
Giải pháp được chọn
In case of problems with updating then best is to go to the official Mozilla website and download the latest version there.
You can find the full version of the current Firefox release (50.1.0) in all languages and all operating systems here:
Version 50.1.0, first offered to Release channel users on December 13, 2016
Bingo! Downloading and installing 51.1.0 cleared that up.
Thank you very much again for your help.
You're welcome