-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTMLTableElement's rows order is not tested in wpt #4470
Comments
I believe @annevk opinion was based on misunderstanding my and @foolip's proposal (that it would be based on the rendering). The proposal is:
This matches default rendering, and is strictly less moving of rows than what the spec does today. |
And I guess Blink and WebKit match the current spec, whereas Gecko matches your proposal? But, we want to write web platform tests to confirm? |
Looking at http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=3778 in Firefox Nightly it seems it matches the current spec now also. |
I'd like to work on this. If I understand correctly, there is no compatibility problems between the major browsers and the spec, and we just need the tests? |
That's great! And yeah, I think that's correct. web-platform-tests uses issues for coordination or backlog. If you can address something immediately (i.e., via a PR) there's no need for an issue. |
Hm, it seems like there is already a test for this. The "complicated case" test case asserts the results of the following HTML, which seems to cover the cases discussed here. E.g. it is asserted that all Asserted HTML<table>
<tr id="orphan1"></tr>
<tfoot>
<tr id="foot1row1"></tr>
<tr id="foot1row2"></tr>
<div>
<tr></tr>
</div>
<tr></tr>
</tfoot>
<tr id="orphan2"></tr>
<tfoot>
<tr id="foot2row1"></tr>
<tr id="foot2row2"></tr>
</tfoot>
<tr id="orphan3"></tr>
<tbody>
<tr id="body1row1"></tr>
<tr id="body1row2"></tr>
<div>
<tr></tr>
</div>
<tr></tr>
</tbody>
<tr id="orphan4"></tr>
<tbody>
<tr id="body2row1"></tr>
<tr id="body2row2"></tr>
</tbody>
<tr id="orphan5"></tr>
<thead>
<tr id="head1row1"></tr>
<tr id="head1row2"></tr>
<div>
<tr></tr>
</div>
<tr></tr>
</thead>
<tr id="orphan6"></tr>
<thead>
<tr id="head2row1"></tr>
<tr id="head2row2"></tr>
</thead>
<tr id="orphan7"></tr>
<div>
<tr></tr>
</div>
<tr></tr>
</table> This test is passing in all browsers monitored by wpt.fyi. Shall we just close this ticket? :) |
Thanks, it seems that test was made as part of fixing the bug in Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1264947. So yeah, everything is in order! |
Thank you @muodov for your willingness to dive in and help us close this out! |
Porting from https://www.w3.org/Bugs/Public/show_bug.cgi?id=29018.
The order of rows in that collection is apparently not interoperable between browsers. There are competing proposals, with @foolip and @zcorpan proposing (in https://www.w3.org/Bugs/Public/show_bug.cgi?id=29018#c7):
and @annevk proposing (https://www.w3.org/Bugs/Public/show_bug.cgi?id=29018#c16):
For the record, as of today the standard says
I tend to agree the standard sounds pretty nice and simple, and we should consider just writing tests and filing a Firefox bug, with no spec changes.
The text was updated successfully, but these errors were encountered: