- From: <bugzilla@jessica.w3.org>
- Date: Mon, 22 Aug 2016 17:46:56 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25412 --- Comment #40 from Aryeh Gregor <ayg@aryeh.name> --- Do you think exact behavior in the event of recursion here is likely to have any implications for web compat? Gecko doesn't support it at all and hasn't gotten bug reports (has it?), and other UAs don't agree on the most basic aspects of how it behaves. It doesn't seem likely anyone is relying on it. (But it's still worth speccing because these edge cases can collectively contribute to lack of interop, even if none is important by itself.) Are there any specific edge cases you would like tested? By the way, these issues with recursion are similar to what comes up if you set TreeWalker's .currentNode from the filter, right? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 22 August 2016 17:47:03 UTC