Convert 2 Microsoft SVG-in-HTML tests to testharness.js #7758
Conversation
That's 014 and 015. Drive-by whitespace changes in 002 and 012.
|
There are no owners for this pull request. Please reach out on W3C's irc server (irc.w3.org, port 6665) on channel #testing (web client) to get help with this. Thank you! |
|
The tests fail in Chrome and Firefox. When all results are on wpt.fyi, maybe it'll be easier to decide what to do with these. |
Build PASSEDStarted: 2017-10-13 14:43:06 View more information about this build on: |
|
As far as standardizing format goes, the pull request should probably be approved. But the tests themselves need a review. I'm particularly confused about 015: I don't think there's anything in the HTML parser that is expected to camelCase an HTML element name just because it happens to be a case-insensitive match for an SVG element camelCase name; the case-correction is specific to being in an SVG namespace parsing context. Not sure where's the best place to discuss that. 014 is correct per SVG 1.1 and the HTML parser, but we probably need something added to SVG 2 that lists the now-obsolete elements and requires them to be parsed as SVG. That should probably be an issue filed in https://github.com/w3c/svgwg/issues/ |
|
Thanks @AmeliaBR, I didn't look too hard at the validity, once I know the results I'll get back to your comment to see what changes and issues are needed. |
That's 014 and 015. Drive-by whitespace changes in 002 and 012.