Closed Bug 259044 Opened 16 years ago Closed 15 years ago

Options General Page not auto expanded to include SideBar Switcher Settings.

Categories

(Toolkit :: Add-ons Manager, defect, minor)

x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED WONTFIX

People

(Reporter: rdlymail-moz9bugzilla, Assigned: bugzilla)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3

I am aware that this could be a SideBar Switcher extension problem. However, the
worthy author of that otherwise excellent product has seemingly hidden himself
without email/forum/feedback contact so I must address the problem from this
end. If you know better please advise and, hopefully, pass this to the correct
person.

I use SideBar Switcher 0.4 on FF 0.9.3. The SideBar Switcher Settings controls
are only partly visible in the FF Options 'General' panel. This can be expanded
manually to show fully but it is irritating to have to do that sort of thing
except for long lists which should be scrollable anyway. It should be done
automatically.

Reproducible: Always
Steps to Reproduce:
1. Install FF 9.03
2. Install otherwise excellent extension SideBar Switcher
3. Go to Tools>Options>General
4) SBS is half displayed at bottom of panel

Actual Results:  
SBS is half displayed at bottom of panel

Expected Results:  
Either FF or the extension should have slightly deepened the panel to fully
include the complete 'SideBar Orientation' box.

If large additions are made to the panels then they should switch to scrollable.

I am using the default theme for FF 0.9.3

I almost made this a severity 'trivial' but then decided that it reflected a
lapse not in content but in processing standards and/or procedures and as such
is not really trivial.

Sorry if this seems like a sledgehammer attacking a nut. I would have initially
prefered a friendly note by response box or email to the extension author.
This is invalid now, due to the separate Extension Manager.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
This problem still applies at FF 1.0.2 and the original closure was, to put it
discretely, not completely ethical, in that as an end user I was not familiar
with the components list (was EM in it then?) and EM was certainly still part of
FF then just as it is now.

Please can some tweaking be done in this area at some stage when someone is in
there?
Status: RESOLVED → UNCONFIRMED
Component: Preferences → Extension/Theme Manager
Resolution: INVALID → ---
The extension manager (Tools->Extensions) provides a mechanism for extensions to
have their own preference windows.  Extensions should not overlay the main
application menu anymore (nor should they have in the first place).

Extensions will do dumb things sometimes, but when we've provided a mechanism
for them to not, we're not going to support their bad decisions.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago15 years ago
Resolution: --- → WONTFIX
(In reply to comment #3)
> The extension manager (Tools->Extensions) provides a mechanism for extensions to
> have their own preference windows.  Extensions should not overlay the main
> application menu anymore (nor should they have in the first place).
> 
> Extensions will do dumb things sometimes, but when we've provided a mechanism
> for them to not, we're not going to support their bad decisions.

That policy (and your response) makes convincing good sense to me.

Is it possible to 

a) Amiably notify the authors of DownLoadManagerTweak and SideBarSwitcher that
their options should be provided only via the standard extension options
facility and/or within their own extension interface?

b) [b]Then[/b] actively prevent 'guest' code from overlaying the main
application menu anymore? Is the current ability to do it a security hole and
should someone raise a bug about that?

Regards, RDL


Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.