- From: Hallvord R. M. Steen <hallvord@opera.com>
- Date: Tue, 12 Feb 2008 03:11:41 +0100
- To: "Jonas Sicking" <jonas@sicking.cc>
- Cc: "Charles McCathieNevile" <chaals@opera.com>, "Web API WG (public)" <public-webapi@w3.org>
On Tue, 12 Feb 2008 02:56:12 +0100, Jonas Sicking <jonas@sicking.cc> wrote: >>> http://tc.labs.opera.com/apis/XMLHttpRequest/responseXML/009.htm >> There is a possible web content compatibility issue here if functions >> that expect documents may throw on null input. For example, does >> xsltprocessor.importStylesheet(null) throw? If it does the >> implementation we test for might break content that expects a broken >> document error to be handled differently. > > At least in firefox xsltprocess.importStylesheet will throw if given > anything but a valid XSLT stylesheet. I.e. null, random XML, and > <parseerror> will throw. Thanks, in that case it should be pretty web-compatible to change from empty document to null. Unless I'm overlooking some other use case that might require an empty doc. -- Hallvord R. M. Steen Core QA JavaScript tester, Opera Software http://www.opera.com/ Opera - simply the best Internet experience
Received on Tuesday, 12 February 2008 02:11:02 UTC