In review for WPT /accname/name/comp_text_node.html
<h2 class="ex" data-expectedlabel="heading label" data-testname="heading with text/comment/text nodes" id="labelTest1">
heading<!-- with non-text node splitting concatenated text nodes -->label<!-- [sic] no extra spaces around first comment -->
</h2>
WebKit results in PASS: expected "heading label" and got "heading label"
Chrome results in FAIL: expected "heading label" but got "headinglabel"
Discrepancy is that the AccName comp uses the term node, and these are two text nodes joined by a comment node and no additional whitespace.
Even if WebKit is to spec here, Chromium's implementation allows authors to choose whether they want the space, while WebKit always joins on a space, according to the spec. Worth revisiting?
Skipping this test in WPT for now.
- If this results in a spec change, please raise a new issue in AccName to update the WPT test, or
- If this results in no spec change, pleas assign back to me and I'll used this one to reinstate the test as written, confirming the WebKit behavior, not the Chromium behavior.
In review for WPT
/accname/name/comp_text_node.htmlWebKit results in
PASS: expected "heading label" and got "heading label"Chrome results in
FAIL: expected "heading label" but got "headinglabel"Discrepancy is that the AccName comp uses the term node, and these are two text nodes joined by a comment node and no additional whitespace.
Even if WebKit is to spec here, Chromium's implementation allows authors to choose whether they want the space, while WebKit always joins on a space, according to the spec. Worth revisiting?
Skipping this test in WPT for now.