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

• From: <bugzilla@jessica.w3.org>
• Date: Wed, 30 Sep 2015 21:20:17 +0000
• To: public-webapps-bugzilla@w3.org
• Message-ID: <bug-23460-2532-FIuNRuGEfV@http.www.w3.org/Bugs/Public/>

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

--- Comment #6 from Arkadiusz Michalski (Spirit) <crimsteam@gmail.com> ---
(In reply to Travis Leithead [MSFT] from comment #3)

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

Hmm, Element.insertAdjacentHTML() makes parsing, all parsing APIs throw for
XML, even innerHTML/outerHTML when setting, Range.createContextualFragment() or
DOMParser.parseFromString() (this last expose error document instead of throw
error). 

Problem exist only for serialization stuff, like innerHTML/outerHTML getting
and XMLSerializer.serializeToString().

-- 
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 21:20:19 UTC