[Bug 27122] MutationObserver.observe(node, {}) should throw from bugzilla@jessica.w3.org on 2014-10-21 (public-webapps-bugzilla@w3.org from October 2014)

From: <bugzilla@jessica.w3.org>
Date: Tue, 21 Oct 2014 23:11:50 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-27122-2532-VCjfgsJkps@http.www.w3.org/Bugs/Public/>

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

--- Comment #11 from Olli Pettay <bugs@pettay.fi> ---
That is mostly hypothetical, and if new features is to be added, we should make
sure that backwards compatibility is sane.

Is there any reason to not throw early if observe() doesn't do anything sane?
(and it used to do that)

Why would newFeature be handled differently to existing properties where we
throw in some cases.

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

Received on Tuesday, 21 October 2014 23:11:51 UTC