gecko-dev/widget/tests/window_state_windows.xul
Andrew McCreight 5dec0e0beb Bug 1432992, part 1 - Remove definitions of Ci, Cr, Cc, and Cu. r=florian
This patch was autogenerated by my decomponents.py

It covers almost every file with the extension js, jsm, html, py,
xhtml, or xul.

It removes blank lines after removed lines, when the removed lines are
preceded by either blank lines or the start of a new block. The "start
of a new block" is defined fairly hackily: either the line starts with
//, ends with */, ends with {, <![CDATA[, """ or '''. The first two
cover comments, the third one covers JS, the fourth covers JS embedded
in XUL, and the final two cover JS embedded in Python. This also
applies if the removed line was the first line of the file.

It covers the pattern matching cases like "var {classes: Cc,
interfaces: Ci, utils: Cu, results: Cr} = Components;". It'll remove
the entire thing if they are all either Ci, Cr, Cc or Cu, or it will
remove the appropriate ones and leave the residue behind. If there's
only one behind, then it will turn it into a normal, non-pattern
matching variable definition. (For instance, "const { classes: Cc,
Constructor: CC, interfaces: Ci, utils: Cu } = Components" becomes
"const CC = Components.Constructor".)

MozReview-Commit-ID: DeSHcClQ7cG

--HG--
extra : rebase_source : d9c41878036c1ef7766ef5e91a7005025bc1d72b
2018-02-06 09:36:57 -08:00

85 lines
2.8 KiB
XML

<?xml version="1.0"?>
<!-- This Source Code Form is subject to the terms of the Mozilla Public
- License, v. 2.0. If a copy of the MPL was not distributed with this
- file, You can obtain one at http://mozilla.org/MPL/2.0/. -->
<?xml-stylesheet href="chrome://global/skin" type="text/css"?>
<?xml-stylesheet href="chrome://mochikit/content/tests/SimpleTest/test.css" type="text/css"?>
<window id="NativeWindow"
xmlns="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"
width="300"
height="300"
onload="onLoad();"
title="Window State Tests">
<script type="application/javascript"
src="chrome://mochikit/content/tests/SimpleTest/SimpleTest.js" />
<script type="application/javascript">
<![CDATA[
ChromeUtils.import("resource://gre/modules/XPCOMUtils.jsm");
SimpleTest.waitForExplicitFinish();
function onLoad() {
var wm = Cc["@mozilla.org/appshell/window-mediator;1"].getService(Ci.nsIWindowMediator);
var win = wm.getMostRecentWindow("navigator:browser");
/*
switch(win.windowState) {
case win.STATE_FULLSCREEN:
dump("STATE_FULLSCREEN \n");
break;
case win.STATE_MAXIMIZED:
dump("STATE_MAXIMIZED \n");
break;
case win.STATE_MINIMIZED:
dump("STATE_MINIMIZED \n");
break;
case win.STATE_NORMAL:
dump("STATE_NORMAL \n");
break;
}
*/
// Make sure size mode changes are reflected in the widget.
win.restore();
ok(win.windowState == win.STATE_NORMAL, "window state is restored.");
win.minimize();
ok(win.windowState == win.STATE_MINIMIZED, "window state is minimized.");
// Windows resizes children to 0x0. Code in nsWindow filters these changes out. Without
// this all sorts of screwy things can happen in child widgets.
ok(document.height > 0, "document height should not be zero for a minimized window!");
ok(document.width > 0, "document width should not be zero for a minimized window!");
// Make sure size mode changes are reflected in the widget.
win.restore();
ok(win.windowState == win.STATE_NORMAL, "window state is restored.");
win.maximize();
ok(win.windowState == win.STATE_MAXIMIZED, "window state is maximized.");
win.restore();
ok(win.windowState == win.STATE_NORMAL, "window state is restored.");
/*
dump(win.screenX + "\n");
win.minimize();
dump(win.screenX + "\n");
win.restore();
dump(win.screenX + "\n");
*/
SimpleTest.finish();
}
]]>
</script>
<body xmlns="http://www.w3.org/1999/xhtml">
<p id="display"></p>
<div id="content" style="display: none"></div>
<pre id="test"></pre>
</body>
</window>