<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Brett Zamir wrote:
<blockquote cite="mid:4A13C104.2030306@yahoo.com" type="cite">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
Jonas Sicking wrote:
<blockquote
cite="mid:63df84f0905200107l27b6a614w156ac908494bd267@mail.gmail.com"
type="cite">
<pre wrap="">On Wed, May 20, 2009 at 12:49 AM, Maciej Stachowiak <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:mjs@apple.com"><mjs@apple.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On May 19, 2009, at 11:49 PM, Jonas Sicking wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Mon, May 18, 2009 at 5:45 AM, Brett Zamir <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:brettz9@yahoo.com"><brettz9@yahoo.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Has any thought been given to standardizing on at least a part of DOM
Level
3 Load and Save in HTML5?
</pre>
</blockquote>
<pre wrap="">The Load and Save APIs in DOM 3 are much too complicated IMHO so I'd
like to see something simpler standardized.
We've had parsing and serializing APIs in Firefox for ages. Would be
very exited to see someone put in effort to get their API cleaned up
and standardized.
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://developer.mozilla.org/En/DOMParser">https://developer.mozilla.org/En/DOMParser</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://developer.mozilla.org/En/XMLSerializer">https://developer.mozilla.org/En/XMLSerializer</a>
</pre>
</blockquote>
<pre wrap="">WebKit actually implements most of these. I think it would make sense to
publish these as a WebApps spec. But these classes don't do any loading or
saving, just parsing and serializing.
</pre>
</blockquote>
<pre wrap=""><!---->
Doesn't XMLHttpRequest do all the load/save that is needed? I don't
know how would could standardize save beyond that without relying on
something like WebDAV.
</pre>
<blockquote type="cite">
<pre wrap="">Document.load would be the simplified
load/save method that it would make sense to standardize IMO, since Firefox
has it and it is needed for Web compatibility. I am concerned though that
Document.load() allows for synchronous network loads.
</pre>
</blockquote>
<pre wrap=""><!---->
I'm certainly no fan of Document.load() and wish it would go away. In
fact we have decided not to add any additional features such as CORS
or progress event support in order to discourage its use and move
people to XHR instead.
/ Jonas
</pre>
</blockquote>
<br>
Does Ajax at least have theoretical support for loading entities from
an external DTD, as I presume a DOM method must? (Would be nice to hear
from some others on that separate "External document subset support"
thread too, especially to know whether all the browsers are just not
inclined to ever implement this (despite all of the off-web documents
that use them...))<br>
</blockquote>
<br>
Sorry, guess I can answer the first part of my question, yes it is
theoretically possible... Per
<a class="moz-txt-link-freetext" href="http://www.w3.org/TR/XMLHttpRequest/#responsexml">http://www.w3.org/TR/XMLHttpRequest/#responsexml</a> , "Return the XML
response entity body." -> "Parse the response entity body into a
document tree following the rules from the XML specifications."<br>
<br>
But I'm still holding out hope that the ability to at least parse an
external DTD for entities alone would be considered...<br>
<br>
Brett<br>
</body>
</html>