513377 - HTML rendered differently depending on window opener - nsIWindowWatcher vs window.open

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Embedding: APIs, defect)

Description

[Jonathan Griffin (:jgriffin)]

Attachment: testcase-bad-1 (XUL)

Some HTML content is rendered incorrectly in windows opened using nsIWindowWatcher.openWindow(), but correctly in windows opened using window.open().  This problem was discovered in the context of creating an extension to allow reftests to be run over HTTP.

To reproduce:
Download the attached testcase-bad-1.xul.  Launch firefox with the chrome argument and the path to the xul file, e.g., ./firefox -chrome /path/to/testcase-bad-1.xul.  Press Allow if presented with an Internet Security dialog.

The xul window will open two new windows, one opened using nsIWindowWatcher.openWindow(), the other using window.open().  Both new windows will load http://people.mozilla.org/~jgriffin/371561-1.html, but the window opened using nsIWindowWatcher.openWindow() will render the content incorrectly; the green bar which should span the width of the underlying text will only be a few pixels wide.

The problem disappears if "display:inline" is removed from the source content;  load testcase-good.xul to see.

Another problem case is found in testcase-bad-2.xul.  In this case, the height of the yellow div will be too small in the window opened using nsIWindowWatcher.openWindow().  In this case, the problem will disappear if removing the line:

option { height: 0; min-height: 0; }

Comment 1

[Jonathan Griffin (:jgriffin)]

Attachment: testcase-bad-2 (XUL)

Comment 2

[Jonathan Griffin (:jgriffin)]

Attachment: testcase-good (XUL)

Comment 3

[Benjamin Smedberg]

Marking a bunch of bugs in the "Embedding: APIs" component INCOMPLETE in preparation to archive that component. If I have done this incorrectly, please reopen the bugs and move them to a more correct component as we don't have "embedding" APIs any more.