Re: [html-tests] Add tests for <summary>'s activation behavior (#4539) from Domenic Denicola on 2017-01-17 (public-web-platform-tests-notifications@w3.org from January 2017)

From: Domenic Denicola <web-platform-tests-notifications@w3.org>
Date: Tue, 17 Jan 2017 18:10:04 GMT
To: public-web-platform-tests-notifications@w3.org
Message-Id: <<web-platform-tests_issue_4539_1484676604217@w3.org>>

Thanks so much @jugglinmike, that's super-valuable! I added my diagnosis of the Chrome issue in https://bugs.chromium.org/p/chromium/issues/detail?id=681711#c2 .

Now the question becomes, what is our strategy for merging or not merging tests that expose flakiness bugs in engines? Should I work around the Chrome bug (e.g. delay for some time to wait for the page to render and all layout objects to be created before starting the test suite), thus giving Chrome a free pass here? Or should we merge anyway, despite Travis not wanting us to? @gsnedders, @jgraham, thoughts?

View on GitHub: https://github.com/w3c/web-platform-tests/pull/4539#issuecomment-273250209

Received on Tuesday, 17 January 2017 18:10:16 UTC