- From: Jonas Sicking <jonas@sicking.cc>
- Date: Tue, 19 Feb 2008 02:39:56 -0800
- To: Anne van Kesteren <annevk@opera.com>
- Cc: Boris Zbarsky <bzbarsky@mit.edu>, Lachlan Hunt <lachlan.hunt@lachy.id.au>, public-webapi@w3.org
Anne van Kesteren wrote: > > On Tue, 19 Feb 2008 10:43:14 +0100, Boris Zbarsky <bzbarsky@MIT.EDU> wrote: >> The only solution I'm seeing so far to a hanging NSResolver is >> terminating that script at some point. > > Is that what you're doing for treewalker node filters? Yes. > I'm not sure why we should specifically define what to do with a hanging > NSResolver case. I think it should be treated identically to a hanging > script. (Ideally they run forever with the UI still being usable.) Agreed. I think it's outside the scope of the spec to try to deal with this. I think the text about behaving in the face of a hostile NSResolver should be informative rather than normative (not sure if it already is), and possibly live in a security considerations section. / Jonas
Received on Tuesday, 19 February 2008 10:40:27 UTC