On 4/27/15 8:38 PM, Josh Matthews wrote:
https://github.com/servo/servo/wiki/Meeting-2015-04-27
I've mentioned this a few times, but...
For a layout engine, being able to attach an actual testcase to a bug
report is _really_ useful once you get out of "just build it" mode and
into "fix all the bugs in this thing you built" mode. Github issues
simply have no way to do this that I've been able to find. You can put
testcases on jsfiddle or other such services, but it's really hard to do
minimal testcases that way because of all the things those services pull
in, it's impossible to test some things (e.g. parser issues, quirks
mode) because there's little control over the markup, and there are
absolutely no guarantees your testcase will be around in 5 years when
you want to see what that code change was trying to fix.
This is really a problem I expect you'll want to solve at some point if
you want to be able to get useful functionality bug reports and
community QA.
-Boris
_______________________________________________
dev-servo mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-servo
