- From: jugglinmike <web-platform-tests-notifications@w3.org>
- Date: Wed, 08 Feb 2017 22:50:06 GMT
- To: public-web-platform-tests-notifications@w3.org
The like-named test in this file asserts the same behavior using a different attribute name: ```js test(function () { var element = define_new_custom_element(['title']); var instance = document.createElement(element.name); instance.setAttribute('class', 'hello'); assert_array_equals(element.takeLog().types(), ['constructed']); instance.classList.replace('hello', 'world'); assert_array_equals(element.takeLog().types(), []); }, 'replace on DOMTokenList must not enqueue an attributeChanged reaction when replacing a value in an unobserved attribute'); ``` In removing the test, my interpretation was that the specific attribute name was inconsequential and that the behavior under test was limited to whether the reaction was enqueued for *any* unobserved attribute. I'm happy to persist the test with a distinct name, though defining coverage in those terms would suggest the need for many more tests. What would you think about adding more tests for additional attributes? View on GitHub: https://github.com/w3c/web-platform-tests/pull/4767#issuecomment-278488324
Received on Wednesday, 8 February 2017 22:50:17 UTC