- From: <bugzilla@jessica.w3.org>
- Date: Mon, 22 Aug 2016 15:41:15 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25412 --- Comment #39 from Boris Zbarsky <bzbarsky@mit.edu> --- I don't think there is anything wrong with that approach, assuming we actually write decent tests that test the various spec edge cases, check them against implementations, file bugs as needed, and get implementors to agree on what the spec should say. This last step is key: I am willing to remove the recursion change from Gecko, possibly in conjunction with some changes to align to the spec, but I am not willing to do that, then discover that what the spec says is not web-compatible or not willing to be implemented by other UAs and change behavior _again_. I've been burned by that sort of thing too many times in the past. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 22 August 2016 15:41:28 UTC