Re: [whatwg] Proposal for window.DocumentType.prototype.toString

2012-10-29 Thread Ian Hickson
On Mon, 29 Oct 2012, Johan Sundstr�m wrote: > > Serializing a complete HTML document DOM to a string is surprisingly > hard in javascript. As a fairly seasoned javascript hacker I figured > this might do it: > > document.doctype + document.documentElement.outerHTML > > It doesn't. No browser

Re: [whatwg] Proposal for window.DocumentType.prototype.toString

2012-10-29 Thread Ojan Vafai
On Mon, Oct 29, 2012 at 6:17 PM, Boris Zbarsky wrote: > On 10/29/12 8:58 PM, Johan Sundström wrote: > >> Serializing a complete HTML document DOM to a string is surprisingly >> hard in javascript. >> > > I thought there were plans to put innerHTML on Document. Did that go > nowhere? There were

Re: [whatwg] Proposal for window.DocumentType.prototype.toString

2012-10-29 Thread Boris Zbarsky
On 10/29/12 8:58 PM, Johan Sundström wrote: Serializing a complete HTML document DOM to a string is surprisingly hard in javascript. I thought there were plans to put innerHTML on Document. Did that go nowhere? As a fairly seasoned javascript hacker I figured this might do it: document

[whatwg] Proposal for window.DocumentType.prototype.toString

2012-10-29 Thread Johan Sundström
Hi everybody! Serializing a complete HTML document DOM to a string is surprisingly hard in javascript. As a fairly seasoned javascript hacker I figured this might do it: document.doctype + document.documentElement.outerHTML It doesn't. No browser has a useful window.DocumentType.prototype that

Re: [whatwg] URL: file: URLs

2012-10-29 Thread Boris Zbarsky
On 10/29/12 10:53 AM, Anne van Kesteren wrote: But at that point in a URL you cannot have a path. A path starts with a slash after the host. The point is that on Windows, Gecko parses file://c:/something as file:///c:/something As in, it's an exception to the general "if there are two slashe

Re: [whatwg] URL: file: URLs

2012-10-29 Thread Anne van Kesteren
On Mon, Oct 29, 2012 at 3:13 PM, Boris Zbarsky wrote: > On 10/29/12 5:00 AM, Anne van Kesteren wrote: >> Maybe I should introduce a "file host state" that supports colons in >> the host name (or special case the "host state" further, but the >> former seems cleaner). > > I don't think that's parti

Re: [whatwg] URL: file: URLs

2012-10-29 Thread Boris Zbarsky
On 10/29/12 5:00 AM, Anne van Kesteren wrote: But note that it would be a bit odd of file://c:/ claimed to have a host of "c" with a default port or some such... Maybe I should introduce a "file host state" that supports colons in the host name (or special case the "host state" further, but the

Re: [whatwg] URL: file: URLs

2012-10-29 Thread Anne van Kesteren
On Sun, Oct 28, 2012 at 6:51 PM, Boris Zbarsky wrote: > Same as the comment I quoted? As same as something else? Same as you quoted. > Well, the Gecko parser preserves the host at this stage assuming the URI was > correctly formatted with a host. Again: > > blah://foo/bar => blah://foo/bar