- From: <bugzilla@jessica.w3.org>
- Date: Tue, 22 Apr 2014 15:58:47 +0000
- To: www-dom@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25412
Bug ID: 25412
Summary: Allow some recursion in NodeIterator/TreeWalker
Product: WebAppsWG
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: DOM
Assignee: annevk@annevk.nl
Reporter: ayg@aryeh.name
QA Contact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, Ms2ger@gmail.com, www-dom@w3.org
The effect of the active flag is that if the filter causes anything to be
called that might invoke the filter, an InvalidStateError is thrown. Is it
really necessary to be so strict? This test indicates that Chrome and IE both
allow some amount of recursion before throwing:
http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2957
Firefox seems to behave like the spec, but I think behavior more like Chrome/IE
is preferable, because it's more tolerant of possibly reasonable code. Chrome
allows around 20 layers of recursion in my test, and IE allows 1770 or
something. I'd like to replace the active flag with a counter that caps at
some arbitrary value like 100 or 1000.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 22 April 2014 15:58:53 UTC