- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Tue, 10 Jun 2014 07:56:33 +0200
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: public-script-coord <public-script-coord@w3.org>
On Mon, Jun 9, 2014 at 10:22 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 6/9/14, 4:07 PM, Travis Leithead wrote: >> Would love your clarification. Is this a Chrome bug or a spec bug? > > It's a Chrome bug per the current DOM spec. I would not be opposed changing the specification as we already allow null as a value there (which will then proceed to do nothing). But since most implementations already throw that seems like unwanted churn. -- http://annevankesteren.nl/
Received on Tuesday, 10 June 2014 05:57:01 UTC