[Bug 23460] Make innerHTML/outerHTML getter non-throwing?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23460

--- Comment #3 from Travis Leithead [MSFT] <travil@microsoft.com> ---
Thanks for the repro.

To match implementations, we should probably make innerHTML/outerHTML not
throw. Does this extend to insertAdjacentHTML? (I presume it does.)

It has always seemed strange to me that an XML serialization (specifically
XMLSerializer::serializeToString) doesn't throw when encountering invalid XML).
With innerHTML/outerHTML, there's not a lot of options to allow web devs to
pass flags to control well-formed-ness. However, for serializeToString, we _do_
have an option of providing an option to the function call that might enable a
well-formed check.

Just thinking out loud:
WebIDL:
```
DOMString serializeToString (Node root, optional SerializationOptions options);

dictionary SerializationOptions {
   boolean throwOnXMLError = false;
};
```

WDYT? Would browsers be willing to adopt this? Is this valuable to web devs?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.

Received on Wednesday, 30 September 2015 19:50:58 UTC