Closed
Bug 295349
Opened 20 years ago
Closed 20 years ago
Le Breeze Theme
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: rklemme, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Build Identifier: Firefox 1.0.4 Theme has crashed firefox. Cannot effectively browse. Text is scrambled in upper left of screen, and pull downs only activate blank windows. Clicking in the approximate area of the blank does result in selections, but nothing is viewable. Uninstall - reinstall does not fix crash. Reproducible: Always Steps to Reproduce: 1. Cannot fix problem to begin with. 2. 3. Unable to load any other theme. Firefox safe mode works, however cannot select or unselect any themes to get away from the LeBreeze theme. Was able to "blindly" delete all but default theme in regular mode (no other theme shows but default in safe mode), however Lebreeze still shows up when firefox is started in regular mode.
Comment 1•20 years ago
|
||
This theme hasn't been updated for anything > Firefox 1.0, so it's no surprise that it doesn't work.
Comment 2•20 years ago
|
||
<https://addons.mozilla.org/themes/moreinfo.php?application=firefox&numpg=10&id=439> only mentions that it works for Firefox 1.0, but <http://www.secondagenda.com/ff/> has newer versions available.
<-INVALID? The theme is not supported by FF >1.0 as mentioned in comment #1 but a new version is available per links in comment #2. Shouldn't this be invalid because the issue is caused by a theme/extension which is not designed to work in the reporter's version of FF?
Updated•20 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 4•20 years ago
|
||
All - thanks for the input - I went to the comment #2 site, downloaded and installed that theme, and it solved the problem. I have since uninstalled all themes and work only off of default.
| Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•