This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27466 - https://dvcs.w3.org/hg/innerhtml/raw-file/tip/index.html#concept-serialize link is stale
Summary: https://dvcs.w3.org/hg/innerhtml/raw-file/tip/index.html#concept-serialize li...
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: XHR (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-28 14:13 UTC by Philip Jägenstedt
Modified: 2014-12-08 07:55 UTC (History)
3 users (show)

See Also:

Attachments

Comment 1 Anne 2014-11-28 14:26:04 UTC 
That seems to take a flag. Bit unclear what contexts should not set that flag...
Comment 2 Travis Leithead [MSFT] 2014-12-01 22:46:04 UTC 
From APIs defined in that spec [DOM P&S], innerHTML and outerHTML set the flag, and serializeToString does not.

Basically, you pass true for the flag if you want to have the algorithm throw on invalid XML serialization. So, if send() may throw (and I think it anticipates that possibility) than pass true.
Comment 4 Philip Jägenstedt 2014-12-08 07:55:14 UTC 
Thanks!

https://dvcs.w3.org/hg/innerhtml/raw-file/tip/index.html#dfn-concept-fragment-serializing-algorithm doesn't actually scroll to the right part of the spec, but I'm going to blame ReSpec for that.

Note that Blink always serializes as application/xml, and the discrepancy is why I filed this bug.