Closed
Bug 572563
Opened 14 years ago
Closed 14 years ago
Developer should have the option to open new windows without an Extension Bar
Categories
(Add-on SDK Graveyard :: General, defect)
Add-on SDK Graveyard
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: dbuchner, Assigned: dietrich)
Details
Currently all newly opened instances and pop-ups have an extension bar created in them. There should be an option to prevent this behavior. To replicate, just open any window with window.open(...), you should instantly see the extension bar when it loads.
Assignee | ||
Comment 1•14 years ago
|
||
our code already does the navigator:browser check we talked about on irc. the window in your code sample is featureless but is actually browser.xul (dump the location!) and windowtype == navigator:browser. A couple of issues with open(): 1. if you don't pass "chrome" as a window option, then xul automagically opens your url in a featureless browser window. that's what you're seeing now. 2. if you do pass "chrome" as a window option, window.open barfs. no window is open, and i see nothing dumped to console. !!!. the workaround i found is to call window.openDialog and add "chrome" to your window options param. this loads your URL in a featureless chrome window that is not navigator:browser. i don't think there's anything to fix for this in jetpack, except perhaps bug 571449.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Comment 2•14 years ago
|
||
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product. To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
Version: Trunk → unspecified
You need to log in
before you can comment on or make changes to this bug.
Description
•