- From: <bugzilla@jessica.w3.org>
- Date: Fri, 25 Apr 2014 12:05:06 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25412 --- Comment #20 from Olli Pettay <bugs@pettay.fi> --- (In reply to Aryeh Gregor from comment #19) > Agreed, but I don't see why we should go out of our way to prevent them. As > Boris alluded to in comment 6, there are other places where we have > callbacks, and we don't require recursion guards like this there. And we have other places where we have guards to prevent recursions. For example click() But I could live with the change, and after looking at Gecko code it should be able to deal with this quite easily. However, before the change some more testing with UAs should be done. How do they deal with nested calls. I'm not talking about endless recursion but filter cb just calling prev/nextNode() once or couple of times etc. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 25 April 2014 12:05:08 UTC