On Thu, Feb 19, 2009 at 3:56 PM, Peter Kasting <[email protected]> wrote: > On Thu, Feb 19, 2009 at 3:56 PM, Peter Kasting <[email protected]> > wrote: >> >> To the degree that new upstream tests represent "stuff we're shipping >> should actually work as advertised", I would prefer not to defer it. > > One more I forgot. If we're trying to not diverge from Safari too much (for > web authors' sake), it behooves us to pass tests that they pass if it's > relevant to web compat.
I think I'm with Peter -- we should only defer tests that we really intend to defer. I imagine there are two classes of tests coming in from upstream: - tests that cover regressions changes - tests that cover new features that we don't yet support It's up to a human to mark the second category DEFER, but we shouldn't do it blindly. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
