Closed
Bug 1108196
Opened 10 years ago
Closed 9 years ago
Two extensions fail to work in Firefox 35.0
Categories
(Firefox :: Extension Compatibility, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: sixa369, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:35.0) Gecko/20100101 Firefox/35.0 Build ID: 20141201162954 Steps to reproduce: I simply installed the "beta" 35 desktop version and two extensions fail to work. Actual results: Neither "Firebug" would function, nor the extension "Expire History by Days." I tried disabling them both and re-enabling them, but no joy. Expected results: They should have worked, especially the "Expire History by Days." Firebug I liked, but found I could work around it with the developer tools as packaged. I very much like the option to limit my history to a two day limit, rather than an "all or nothing" choice, and since setting the options to "delete on exit" has proved problematical (the old "Firefox is running as a process... is hanging" issue) it is a kind of issue. It is not a "fake sense of security" issue with me, it is a "not wanting to carry that much history around" kind of thing.
I am on Windows 7 Premium desktop Firefox, 32 bit. I was on FF 35 until last night when I discovered that 35 was not playing nice with some sites using Flash. It was a capricious thing. Many sites worked as normal but some would not render at all. Examples: http://www.wunderground.com/US/WI/La_Crosse.html http://www.weather.com/weather/5day/l/Hustler+WI+54637:4:US I have spent the entire weekend trying to get the Firefox beta 35 to work. What I have found is that *all* extensions fail to work with the exception of Places Maintenance. I can not download any extension Firefox is so famous for. The error is something like "cannot install 'plugin-name' in it's current state." Enabling any extension require a FF restart, even Places Maintenance. Trying to remove an extension fails and must be done manually. First time I have has a problem with a Firefox beta, but it is definitely not ready for prime time. I realize FF is attempting to get away from what we are calling "Proprietary add-ons" but FF 35 in its present state will just fill the Moz Support forums with millions of complaints. I thought you might like this report as "user input." God knows I have tried...I must have downloaded 35 at least a dozen times and then been forced back to 34.0.5. So I am back on 34.0.5 Let me know if anyone else is having these problems or anyone needs more information.
Comment 2•10 years ago
|
||
Can you reproduce these issues in safe mode? http://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode How about on a clean profile? http://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles Note: Please file different issues in separate bugs. Thanks!
Flags: needinfo?(sixa369)
Comment 3•9 years ago
|
||
Incomplete. * No response from reporter in nearly 4 months. * No steps to reproduce. * Multiple issues conflated into one report. Please retest in the current version of Firefox in a brand new profile. If you can still reproduce the issues, read the bug writing guide, then file individual reports for each issue. https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles https://developer.mozilla.org/docs/Mozilla/QA/Bug_writing_guidelines
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Component: Untriaged → Extension Compatibility
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•