Closed Bug 894036 Opened 13 years ago Closed 8 years ago

require('window/utils').open creates empty window, when called without explicit features

Categories

(Add-on SDK Graveyard :: General, defect, P3)

x86_64
Windows 7
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: rfstrobel, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release) Build ID: 20130618035212 Steps to reproduce: require('window/utils').open() called without any arguments on SDK 1.14, FF 22. Actual results: The created window was completely empty (no user interface elements). Upon code inspection, the reason is that serializeFeatures() defaults to an empty string instead of null, which is expected by windowWatcher.openWindow() to create a standard window. Expected results: I expected this call would default to creating a new standard browser window, equivalent to: windowWatcher.openWindow(null, 'chrome://browser/content/browser.xul', null, null, null);
OS: All → Windows 7
Hardware: All → x86_64
Summary: require('window/utils').open creates empty window without explicit features → require('window/utils').open creates empty window, when called without explicit features
This opens a top-level window, I might argue that with no URI it should just throw an exception but I can understand defaulting to the default app UI.
Priority: -- → P3
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.