- From: Kris Krueger <krisk@microsoft.com>
- Date: Tue, 16 Oct 2012 19:26:02 +0000
- To: Simon Pieters <simonp@opera.com>, "public-html-testsuite@w3.org" <public-html-testsuite@w3.org>, Philippe Le Hegaret <plh@w3.org>
- CC: "public-texttracks@w3.org" <public-texttracks@w3.org>
Thanks for the test submission! It looks like the mine type is not set correctly on the server for .vtt files. The type == text/vtt and not text/plain From a net sniff URL Method Result Type /html/tests/submission/Opera/media/track/webvtt/parsing/support/settings-vertical.vtt GET 200 text/plain Philippe can you help get this fixed? -Thx -----Original Message----- From: Simon Pieters [mailto:simonp@opera.com] Sent: Monday, October 15, 2012 8:38 AM To: public-html-testsuite@w3.org Cc: public-texttracks@w3.org Subject: Opera testsuite for <track> and WebVTT Hi, I've pushed the following tests: http://w3c-test.org/html/tests/submission/Opera/media/ This tests the <track> element, the surrounding DOM API, CORS for <track>, parsing of WebVTT, parsing of WebVTT cue data, and WebVTT cue rendering. The rendering tests are reftests (except the adhoc folder which is manual), the rest are testharness.js tests. The tests do not perfectly reflect the latest changes to the specs. Not all tests are expected to pass in Opera. Some tests check that a feature is not supported (e.g. vertical), but that should be fixed. The parser tests have expected result as JSON in the cue data, and a separate JSON file with expected number of cues per file or error if the file is expected to fail to load. The parser cue data tests are generated from html5lib-style dat files. Expected tree is the "WebVTT cue text DOM construction rules" (the cue.getCueAsHTML() document fragment). Enjoy. -- Simon Pieters Opera Software
Received on Tuesday, 16 October 2012 19:27:14 UTC