Skip to content

Commit de26fb3

Browse files
hamishwilleehamishwillee
authored
Fix inline styles in Web/API - x (mdn#5517)
* XDomainRequest.timeout - fix inline styles * XMLDocument.load() fix inline styles * Using XMLHttpRequest: fix inline styles * XRInputSource.gripSpace fix inline styles * XRInputSource - fix inline styles * XRTargetRayMode - fix inline styles * windoworworkerglobalscope/setinterval - fix inline styles * Window.setImmediate - fix inline styles * Window.scrollX - fix inline styles * Window.screenY - fix inline styles * Window.screenX - fix inline styles * Window popstate event - fix inline styles * Window.screenxxxx - fix style by adding specifications macro * Window.open privil. features - fix inline styles * Remove Add-ons broken links. Fix anchor in heading
1 parent 75f0051 commit de26fb3

File tree

15 files changed

+67
-174
lines changed

15 files changed

+67
-174
lines changed

‎files/en-us/web/api/window/open/privileged_features/index.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@
2323
<dt><code>chrome</code></dt>
2424
<dd>If on, the page is loaded as window's only content, without any of the browser's interface elements. There will be no context menu defined by default and none of the standard keyboard shortcuts will work. The page is supposed to provide a user interface of its own, usually this feature is used to open XUL documents (standard dialogs like the JavaScript Console are opened this way).</dd>
2525
<dt><code>dialog</code></dt>
26-
<dd><a href="menusystemcommands.png" title="MenuSystemCommands.png"><img class="internal lwrap" src="menusystemcommands.png" style="float: left;"> </a> The <code>dialog</code> feature removes all icons (restore, minimize, maximize) from the window's titlebar, leaving only the close button. Mozilla 1.2+ and Netscape 7.1 will render the other menu system commands (in FF 1.0 and in NS 7.0x, the command system menu is not identified with the Firefox/NS 7.0x icon on the left end of the titlebar: that's probably a bug. You can access the command system menu with a right-click on the titlebar). Dialog windows are windows which have no minimize system command icon and no maximize/restore down system command icon on the titlebar nor in correspondent menu item in the command system menu. They are said to be dialog because their normal, usual purpose is to only notify info and to be dismissed, closed. On Mac systems, dialog windows have a different window border and they may get turned into a sheet.</dd>
26+
<dd><a href="menusystemcommands.png" title="MenuSystemCommands.png"><img class="internal lwrap" src="menusystemcommands.png"></a> The <code>dialog</code> feature removes all icons (restore, minimize, maximize) from the window's titlebar, leaving only the close button. Mozilla 1.2+ and Netscape 7.1 will render the other menu system commands (in FF 1.0 and in NS 7.0x, the command system menu is not identified with the Firefox/NS 7.0x icon on the left end of the titlebar: that's probably a bug. You can access the command system menu with a right-click on the titlebar). Dialog windows are windows which have no minimize system command icon and no maximize/restore down system command icon on the titlebar nor in correspondent menu item in the command system menu. They are said to be dialog because their normal, usual purpose is to only notify info and to be dismissed, closed. On Mac systems, dialog windows have a different window border and they may get turned into a sheet.</dd>
2727
<dt><code>modal</code></dt>
2828
<dd>If on, the new window is said to be modal. The user cannot return to the main window until the modal window is closed. A typical modal window is created by the <a href="/en-US/docs/Web/API/Window/alert">alert() function</a>.</dd>
2929
<dd>The exact behavior of modal windows depends on the platform and on the Mozilla release version.

‎files/en-us/web/api/window/popstate_event/index.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ <h2 id="When_popstate_is_sent">When popstate is sent</h2>
7272
<li>If the <strong>new-entry</strong> doesn't have persisted user state and its URL's fragment is non-<code>null</code>, the document is scrolled to that fragment.</li>
7373
<li>Next, <strong>current-entry</strong> is set to <strong>new-entry</strong>. The destination entry is now considered to be current.</li>
7474
<li>If <strong>new-entry</strong> has serialized state information saved with it, that information is deserialized into {{domxref("History.state")}}; otherwise, <code>state</code> is <code>null</code>.</li>
75-
<li><span style="color: #229922;">If the value of <code>state</code> changed, the <code>popstate</code> event is sent to the document.</span></li>
75+
<li>If the value of <code>state</code> changed, the <code>popstate</code> event is sent to the document.</li>
7676
<li>Any persisted user state is restored, if the browser chooses to do so.</li>
7777
<li>If the original and new entry's shared the same document, but had different fragments in their URLs, send the {{domxref("Window.hashchange_event", "hashchange")}} event to the window.</li>
7878
</ol>

‎files/en-us/web/api/window/screenleft/index.html

Lines changed: 2 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -77,22 +77,8 @@ <h2 id="Examples">Examples</h2>
7777

7878
<h2 id="Specifications">Specifications</h2>
7979

80-
<table class="standard-table" style="height: 49px; width: 1000px;">
81-
<thead>
82-
<tr>
83-
<th scope="col">Specification</th>
84-
<th scope="col">Status</th>
85-
<th scope="col">Comment</th>
86-
</tr>
87-
</thead>
88-
<tbody>
89-
<tr>
90-
<td>{{ SpecName('CSSOM View', '#dom-window-screenx', 'Window.screenLeft') }}</td>
91-
<td>{{ Spec2('CSSOM View') }}</td>
92-
<td>Initial definition.</td>
93-
</tr>
94-
</tbody>
95-
</table>
80+
<p>{{Specifications}}</p>
81+
9682

9783
<h2 id="Browser_compatibility">Browser compatibility</h2>
9884

‎files/en-us/web/api/window/screentop/index.html

Lines changed: 1 addition & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -77,22 +77,7 @@ <h2 id="Examples">Examples</h2>
7777

7878
<h2 id="Specifications">Specifications</h2>
7979

80-
<table class="standard-table" style="height: 49px; width: 1000px;">
81-
<thead>
82-
<tr>
83-
<th scope="col">Specification</th>
84-
<th scope="col">Status</th>
85-
<th scope="col">Comment</th>
86-
</tr>
87-
</thead>
88-
<tbody>
89-
<tr>
90-
<td>{{ SpecName('CSSOM View', '#dom-window-screeny', 'Window.screenTop') }}</td>
91-
<td>{{ Spec2('CSSOM View') }}</td>
92-
<td>Initial definition.</td>
93-
</tr>
94-
</tbody>
95-
</table>
80+
<p>{{Specifications}}</p>
9681

9782
<h2 id="Browser_compatibility">Browser compatibility</h2>
9883

‎files/en-us/web/api/window/screenx/index.html

Lines changed: 1 addition & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -80,22 +80,7 @@ <h2 id="Examples">Examples</h2>
8080

8181
<h2 id="Specifications">Specifications</h2>
8282

83-
<table class="standard-table" style="height: 49px; width: 1000px;">
84-
<thead>
85-
<tr>
86-
<th scope="col">Specification</th>
87-
<th scope="col">Status</th>
88-
<th scope="col">Comment</th>
89-
</tr>
90-
</thead>
91-
<tbody>
92-
<tr>
93-
<td>{{ SpecName('CSSOM View', '#dom-window-screenx', 'Window.screenX') }}</td>
94-
<td>{{ Spec2('CSSOM View') }}</td>
95-
<td>Initial definition.</td>
96-
</tr>
97-
</tbody>
98-
</table>
83+
<p>{{Specifications}}</p>
9984

10085
<h2 id="Browser_compatibility">Browser compatibility</h2>
10186

‎files/en-us/web/api/window/screeny/index.html

Lines changed: 1 addition & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -66,22 +66,7 @@ <h2 id="Examples">Examples</h2>
6666

6767
<h2 id="Specifications">Specifications</h2>
6868

69-
<table class="standard-table" style="height: 49px; width: 1000px;">
70-
<thead>
71-
<tr>
72-
<th scope="col">Specification</th>
73-
<th scope="col">Status</th>
74-
<th scope="col">Comment</th>
75-
</tr>
76-
</thead>
77-
<tbody>
78-
<tr>
79-
<td>{{ SpecName('CSSOM View', '#dom-window-screeny', 'Window.screenY') }}</td>
80-
<td>{{ Spec2('CSSOM View') }}</td>
81-
<td>Initial definition.</td>
82-
</tr>
83-
</tbody>
84-
</table>
69+
<p>{{Specifications}}</p>
8570

8671
<h2 id="Browser_compatibility">Browser compatibility</h2>
8772

‎files/en-us/web/api/window/scrollx/index.html

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -53,10 +53,7 @@ <h2 id="Example">Example</h2>
5353

5454
<h2 id="Notes">Notes</h2>
5555

56-
<p><span style="line-height: 1.572;">The </span><code
57-
style="font-size: 14px;">pageXOffset</code><span style="line-height: 1.572;"> property
58-
is an alias for the </span><code style="font-size: 14px;">scrollX</code><span
59-
style="line-height: 1.572;"> property:</span></p>
56+
<p>The <code>pageXOffset</code> property is an alias for the <code>scrollX</code> property:</p>
6057

6158
<pre>window.pageXOffset == window.scrollX; // always true</pre>
6259

‎files/en-us/web/api/window/setimmediate/index.html

Lines changed: 13 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,14 @@
22
title: Window.setImmediate()
33
slug: Web/API/Window/setImmediate
44
tags:
5-
- API
6-
- HTML DOM
7-
- Method
8-
- Non-standard
9-
- Reference
10-
- Window
11-
- setImmediate
12-
- Polyfill
5+
- API
6+
- HTML DOM
7+
- Method
8+
- Non-standard
9+
- Reference
10+
- Window
11+
- setImmediate
12+
- Polyfill
1313
browser-compat: api.Window.setImmediate
1414
---
1515
<div>{{APIRef("HTML DOM")}}{{Non-standard_header}}</div>
@@ -21,7 +21,7 @@
2121
<div class="note">This method is not expected to become standard, and is only implemented
2222
by recent builds of Internet Explorer and Node.js 0.10+. It meets resistance both from
2323
<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=686201">Gecko</a> (Firefox) and <a
24-
href="http://code.google.com/p/chromium/issues/detail?id=146172">Webkit</a>
24+
href="https://code.google.com/p/chromium/issues/detail?id=146172">Webkit</a>
2525
(Google/Apple).</div>
2626

2727
<h2 id="Syntax">Syntax</h2>
@@ -41,19 +41,18 @@ <h2 id="Syntax">Syntax</h2>
4141
<h2 id="Notes">Notes</h2>
4242

4343
<p>The {{DOMxRef("Window.clearImmediate", "clearImmediate")}} method can be used to clear
44-
the immediate actions, just like {{DOMxRef("Window.clearTimeout", "clearTimeout")}} for
45-
{{DOMxRef("window.setTimeout", "setTimeout")}}.</p>
44+
the immediate actions, just like {{DOMxRef("WindowOrWorkerGlobalScope/clearTimeout", "clearTimeout")}} for
45+
{{DOMxRef("WindowOrWorkerGlobalScope/setTimeout", "setTimeout")}}.</p>
4646

4747
<p>This method can be used instead of the <code>setTimeout(fn, 0)</code> method to execute
4848
<a
49-
href="http://www.nczonline.net/blog/2009/08/11/timed-array-processing-in-javascript/">heavy
49+
href="https://www.nczonline.net/blog/2009/08/11/timed-array-processing-in-javascript/">heavy
5050
operations</a>. </p>
5151

5252
<p>The feature can be emulated in a few different ways:</p>
5353

5454
<ul>
55-
<li><span style="line-height: 22px;">{{DOMxRef("Window.postMessage",
56-
"postMessage")}} </span>can be used to trigger an immediate but yielding callback.
55+
<li>{{DOMxRef("Window.postMessage", "postMessage")}} can be used to trigger an immediate but yielding callback.
5756
Do note that Internet Explorer 8 includes a synchronous version of
5857
<code>postMessage</code>, which means it cannot be used as a fallback.</li>
5958
<li>{{DOMxRef("MessageChannel")}} can be used reliably inside of Web Workers whereas the

‎files/en-us/web/api/windoworworkerglobalscope/setinterval/index.html

Lines changed: 23 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -2,18 +2,18 @@
22
title: WindowOrWorkerGlobalScope.setInterval()
33
slug: Web/API/WindowOrWorkerGlobalScope/setInterval
44
tags:
5-
- API
6-
- Gecko
7-
- HTML DOM
8-
- Intervals
9-
- JavaScript timers
10-
- MakeBrowserAgnostic
11-
- Method
12-
- NeedsMarkupWork
13-
- Timers
14-
- WindowOrWorkerGlobalScope
15-
- setInterval
16-
- Polyfill
5+
- API
6+
- Gecko
7+
- HTML DOM
8+
- Intervals
9+
- JavaScript timers
10+
- MakeBrowserAgnostic
11+
- Method
12+
- NeedsMarkupWork
13+
- Timers
14+
- WindowOrWorkerGlobalScope
15+
- setInterval
16+
- Polyfill
1717
browser-compat: api.WindowOrWorkerGlobalScope.setInterval
1818
---
1919
<div>{{APIRef("HTML DOM")}}</div>
@@ -41,7 +41,7 @@ <h3 id="Parameters">Parameters</h3>
4141
<dt><code>code</code></dt>
4242
<dd>An optional syntax allows you to include a string instead of a function, which is
4343
compiled and executed every <code>delay</code> milliseconds. This syntax is <em>not
44-
recommended</em> for the same reasons that make using {{jsxref("eval", "eval()")}} a
44+
recommended</em> for the same reasons that make using {{jsxref("Global_Objects/eval", "eval()")}} a
4545
security risk.</dd>
4646
<dt><code>delay</code>{{optional_inline}}</dt>
4747
<dd>The time, in milliseconds (thousandths of a second), the timer should delay in
@@ -56,7 +56,7 @@ <h3 id="Parameters">Parameters</h3>
5656
<p><strong>Note</strong>: Passing additional arguments to <code>setInterval()</code> in
5757
the first syntax does not work in Internet Explorer 9 and earlier. If you want to
5858
enable this functionality on that browser, you must use a polyfill (see the <a
59-
href="#Callback_arguments">Callback arguments</a> section).</p>
59+
href="#callback_arguments">Callback arguments</a> section).</p>
6060
</div>
6161

6262
<h3 id="Return_value">Return value</h3>
@@ -139,7 +139,7 @@ <h3 id="Example_2_Alternating_two_colors">Example 2: Alternating two colors</h3>
139139
<h3 id="Example_3_Typewriter_simulation">Example 3: Typewriter simulation</h3>
140140

141141
<p>The following example simulates typewriter by first clearing and then slowly
142-
typing content into the <a href="/en-US/docs/DOM/NodeList"><code>NodeList</code></a>
142+
typing content into the <a href="/en-US/docs/Web/API/NodeList"><code>NodeList</code></a>
143143
that matches a specified group of selectors.</p>
144144

145145
<pre class="brush:html">&lt;!DOCTYPE html&gt;
@@ -300,7 +300,7 @@ <h3 id="Example_3_Typewriter_simulation">Example 3: Typewriter simulation</h3>
300300
&lt;/html&gt;</pre>
301301

302302
<p><a href="/files/3997/typewriter.html">View this demo in action</a>. See also: <a
303-
href="/en-US/docs/DOM/window.clearInterval"><code>clearInterval()</code></a>.</p>
303+
href="/en-US/docs/Web/API/WindowOrWorkerGlobalScope/clearInterval"><code>clearInterval()</code></a>.</p>
304304

305305
<h2 id="Callback_arguments">Callback arguments</h2>
306306

@@ -366,15 +366,14 @@ <h2 id="Callback_arguments">Callback arguments</h2>
366366
<p>Starting in Gecko 5.0 {{geckoRelease("5.0")}}, intervals are clamped to fire no more
367367
often than once per second in inactive tabs.</p>
368368

369-
<h2 id="The_this_problem">The "<a
370-
href="/en-US/docs/Web/JavaScript/Reference/Operators/this"><code>this</code></a>"
371-
problem</h2>
369+
370+
<h2 id="The_this_problem">The "this" problem</h2>
372371

373372
<p>When you pass a method to <code>setInterval()</code> or any other function, it is
374373
invoked with the wrong <a
375374
href="/en-US/docs/Web/JavaScript/Reference/Operators/this"><code>this</code></a>
376375
value. This problem is explained in detail in the <a
377-
href="/en-US/docs/Web/JavaScript/Reference/Operators/this#As_an_object_method">JavaScript
376+
href="/en-US/docs/Web/JavaScript/Reference/Operators/this#as_an_object_method">JavaScript
378377
reference</a>.</p>
379378

380379
<h3 id="Explanation">Explanation</h3>
@@ -414,7 +413,7 @@ <h3 id="A_possible_solution">A possible solution</h3>
414413
<p>A possible way to solve the "<code>this</code>" problem is to replace the two native
415414
<code>setTimeout()</code> or <code>setInterval()</code> global functions with two
416415
<em>non-native</em> ones that enable their invocation through the <a
417-
href="/en-US/docs/JavaScript/Reference/Global_Objects/Function/call"><code>Function.prototype.call</code></a>
416+
href="/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/call"><code>Function.prototype.call</code></a>
418417
method. The following example shows a possible replacement:</p>
419418

420419
<pre class="brush:js">// Enable the passage of the 'this' object through the JavaScript timers
@@ -438,7 +437,7 @@ <h3 id="A_possible_solution">A possible solution</h3>
438437
<div class="note">These two replacements also enable the HTML5 standard passage of
439438
arbitrary arguments to the callback functions of timers in IE. So they can be used as
440439
<em>non-standard-compliant</em> polyfills also. See the <a
441-
href="#Callback_arguments">callback arguments paragraph</a> for a
440+
href="#callback_arguments">callback arguments paragraph</a> for a
442441
<em>standard-compliant</em> polyfill.</div>
443442

444443
<p>New feature test:</p>
@@ -482,17 +481,6 @@ <h2 id="MiniDaemon_-_A_framework_for_managing_timers">MiniDaemon - A framework f
482481
problem</a> for details). The following code is also <a
483482
href="https://github.com/madmurphy/minidaemon.js">available on GitHub</a>.</p>
484483

485-
<div class="note">For a more complex but still modular version of it
486-
(<code><em>Daemon</em></code>) see <a
487-
href="/en-US/Add-ons/Code_snippets/Timers/Daemons">JavaScript Daemons Management</a>.
488-
This more complex version is nothing but a big and scalable collection of methods for
489-
the <code><em>Daemon</em></code> constructor. However, the <code><em>Daemon</em></code>
490-
constructor itself is nothing but a clone of <code><em>MiniDaemon</em></code> with an
491-
added support for <em>init</em> and <em>onstart</em> functions declarable during the
492-
instantiation of the <code><em>daemon</em></code>. <strong>So the
493-
<code><em>MiniDaemon</em></code> framework remains the recommended way for simple
494-
animations</strong>, because <code><em>Daemon</em></code> without its collection of
495-
methods is essentially a clone of it.</div>
496484

497485
<h3 id="minidaemon.js">minidaemon.js</h3>
498486

@@ -597,7 +585,7 @@ <h4 id="Arguments">Arguments</h4>
597585
arguments</strong>: <em>index</em> (the iterative index of each invocation),
598586
<em>length</em> (the number of total invocations assigned to the <em>daemon</em> -
599587
finite or <a
600-
href="/en-US/docs/JavaScript/Reference/Global_Objects/Infinity"><code>Infinity</code></a>)
588+
href="/en-US/docs/Web/JavaScript/Reference/Global_Objects/Infinity"><code>Infinity</code></a>)
601589
and <em>backwards</em> (a boolean expressing whether the <em>index</em> is increasing
602590
or decreasing). It is something like <em>callback</em>.call(<em>thisObject</em>,
603591
<em>index</em>, <em>length</em>, <em>backwards</em>). <strong>If the callback function
@@ -624,7 +612,7 @@ <h4 id="MiniDaemon_instances_properties"><code>MiniDaemon</code> instances prope
624612
<dd>The function that is repeatedly invoked (read/write). It is called with three
625613
arguments: <em>index</em> (the iterative index of each invocation), <em>length</em>
626614
(the number of total invocations assigned to the daemon - finite or <a
627-
href="/en-US/docs/JavaScript/Reference/Global_Objects/Infinity"><code>Infinity</code></a>)
615+
href="/en-US/docs/Web/JavaScript/Reference/Global_Objects/Infinity"><code>Infinity</code></a>)
628616
and backwards (a boolean expressing whether the <em>index</em> is decreasing or not) –
629617
see above. If the <code>myDaemon.task</code> function returns a <code>false</code>
630618
value the <em>daemon</em> is paused.</dd>
@@ -792,15 +780,8 @@ <h2 id="See_also">See also</h2>
792780

793781
<ul>
794782
<li>A polyfill of <code>setInterval</code> which allows passing arguments to the callback is available in <a href="https://github.com/zloirock/core-js#settimeout-and-setinterval"><code>core-js</code></a></li>
795-
<li><a href="/en-US/Add-ons/Code_snippets/Timers">JavaScript timers</a></li>
796783
<li>{{domxref("WindowOrWorkerGlobalScope.setTimeout")}}</li>
797784
<li>{{domxref("WindowOrWorkerGlobalScope.clearTimeout")}}</li>
798785
<li>{{domxref("WindowOrWorkerGlobalScope.clearInterval")}}</li>
799786
<li>{{domxref("window.requestAnimationFrame")}}</li>
800-
<li><a href="/en-US/Add-ons/Code_snippets/Timers/Daemons"><em>Daemons</em>
801-
management</a></li>
802787
</ul>
803-
804-
<div id="gtx-trans" style="position: absolute; left: 164px; top: 272px;">
805-
<div class="gtx-trans-icon"></div>
806-
</div>

‎files/en-us/web/api/xdomainrequest/timeout/index.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@
1818

1919
<h2 id="Syntax">Syntax</h2>
2020

21-
<pre style="font-size: 14px;">xdr.timeout = milliseconds;</pre>
21+
<pre class="brush: js">xdr.timeout = milliseconds;</pre>
2222

2323
<p>The default value is 0.</p>
2424

‎files/en-us/web/api/xmldocument/load/index.html

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,20 +13,18 @@
1313
---
1414
<p>{{APIRef("DOM")}}{{Non-standard_Header}}{{Deprecated_Header}}</p>
1515

16-
<p><code>document.load()</code> is a part of an old version of the W3C <a href="https://www.w3.org/TR/2003/WD-DOM-Level-3-LS-20030619/load-save.html#LS-DocumentLS">DOM Level 3 Load &amp; Save module</a>. Can be used with {{DOMxRef("document.async")}} to indicate whether the request is synchronous or asynchronous (the default). As of at least Gecko 1.9, this no longer supports cross-site loading of documents (Use {{DOMxRef("XMLHttpRequest")}} or {{DOMxRef("WindowOrWorkerGlobalScope.fetch", "fetch()")}} instead).</p>
16+
<p><code>document.load()</code> is a part of an old version of the W3C <a href="https://www.w3.org/TR/2003/WD-DOM-Level-3-LS-20030619/load-save.html#LS-DocumentLS">DOM Level 3 Load &amp; Save module</a>. Can be used with {{DOMxRef("XMLDocument.async")}} to indicate whether the request is synchronous or asynchronous (the default). As of at least Gecko 1.9, this no longer supports cross-site loading of documents (Use {{DOMxRef("XMLHttpRequest")}} or {{DOMxRef("WindowOrWorkerGlobalScope.fetch", "fetch()")}} instead).</p>
1717

1818
<h2 id="Examples">Examples</h2>
1919

20-
<div style="overflow: hidden;">
21-
<pre>var xmlDoc = document.implementation.createDocument("", "test", null);
20+
<pre class="brush: js">var xmlDoc = document.implementation.createDocument("", "test", null);
2221

2322
function documentLoaded (e) {
2423
alert(new XMLSerializer().serializeToString(e.target)); // Gives querydata.xml contents as string
2524
}
2625

2726
xmlDoc.addEventListener("load", documentLoaded, false);
2827
xmlDoc.load('querydata.xml');</pre>
29-
</div>
3028

3129
<p>{{Source("content/xml/tests/load/", "See also the load sample")}} in the XML tests directory. (To test this functionality, create the files on your local disk or on a webserver rather than loading the load.html file from the LXR-generated page, which will serve the text.xml file as HTML.)</p>
3230

0 commit comments

Comments
 (0)