Closed Bug 295237 Opened 19 years ago Closed 19 years ago

PrefWindowVs opened from Extension Manager lack pane switcher (toolbar)

Categories

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

defect

Tracking

()

RESOLVED FIXED
mozilla1.8final

People

(Reporter: jruderman, Assigned: asaf)

Details

Attachments

(1 file, 1 obsolete file)

I tried to write an extension using PrefWindowV and couldn't get the pane
switcher to show up.  If I went to chrome://owo/content/owoOptions.xul in a
browser window, everything worked fine, but if I clicked the Options button in
the Extension Manager, all I could see was the first pane of my options window.

The Extension Manager's cmd_options at
http://lxr.mozilla.org/mozilla/source/toolkit/mozapps/extensions/content/extensions.js#806
does not include "toolbar" as a feature and 
http://lxr.mozilla.org/mozilla/source/toolkit/content/xul.css#998 makes the pane
switcher hidden in windows with chromehidden~="toolbar".

My first instinct is that cmd_options in the Extension Manager should be passing
",toolbar", but I wonder why xul.css specifically instructs preferences windows
to hide their panels when the "toolbar" feature isn't specified in the
openDialog call.
Nominating to block 1.1alpha.  If this isn't fixed in alpha, it will confuse
anyone who tries to make a PrefWindowV-using extension in alpha.  Furthermore,
when this is fixed, it may cause problems for extensions that expect the buggy
behavior.
Flags: blocking1.8b2?
Flags: blocking-aviary1.1?
Summary: PrefWindowVs opened from Extension manager lack toolbars → PrefWindowVs opened from Extension Manager lack pane switcher (toolbar)
mconnor, smedberg,  any thoughts on a fix for this?
See bug 283660, I think the correct solution is to just fix the EM to pass
"toolbar" in the open dialog.
Indeed. We should also respect the instantApply perf before adding the 'modal'
feature.
Assignee: nobody → bugs.mano
OS: Windows XP → All
Priority: -- → P2
Hardware: PC → All
Target Milestone: --- → Firefox1.1
Status: NEW → ASSIGNED
Attached patch patch (obsolete) — Splinter Review
Attachment #184943 - Flags: review?(mconnor)
Comment on attachment 184943 [details] [diff] [review]
patch


>+          var features = "chrome,titlebar,toolbar,centerscreen" + (instantApply ? ",dialog=no" : 
>+",modal");

gah, please ignore the new line here :-/
Attached patch add fallback...Splinter Review
Attachment #184943 - Attachment is obsolete: true
Attachment #184946 - Flags: review?(mconnor)
Attachment #184943 - Flags: review?(mconnor)
hoping there aren't too many extension builders out that that need to rely on
this fix to get pref windows straight. rafael can add to the release note this
to warn anyone who might be...  

b2 -> b3
Flags: blocking1.8b3+
Flags: blocking1.8b2?
Flags: blocking1.8b2-
If I read this right, if instantApply is true then the options opened from
extensions are non-modal, whether they are prefwindow based preferences or not.

So far as I can see there is currently nothing in place to then stop a user from
opening multiple copies of the extensions options.
Yeah, but there's not much we can do about it, at this point (fixing that would
requier at least one more install.rdf's entry)

(...I should also point out that w/o this change prefwindow-v based options
window are not closeable on os x.)
Attachment #184946 - Flags: review?(mconnor) → review+
Attachment #184946 - Flags: approval-aviary1.1a2?
Comment on attachment 184946 [details] [diff] [review]
add fallback...

a=chofmann
Attachment #184946 - Flags: approval-aviary1.1a2? → approval-aviary1.1a2+
Checking in extensions.js;
/cvsroot/mozilla/toolkit/mozapps/extensions/content/extensions.js,v  <-- 
extensions.js
new revision: 1.54; previous revision: 1.53
done
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Flags: blocking-aviary1.1?
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: