gecko-dev/testing/web-platform/tests/svg
Emilio Cobos Álvarez a6845a59a2 Bug 1547619 - Fix :-moz-svg-use-shadow-tree-root pseudo-class. r=violet
Turns out removing the pseudo-class and such ends up not being quite as trivial
as I initially thought, or possible at all, since the fact that the <symbol> is
a <symbol> is observable via selectors, added a test for that.

Differential Revision: https://phabricator.services.mozilla.com/D29131

--HG--
extra : moz-landing-system : lando
2019-04-29 08:04:22 +00:00
..
animations/scripted
coordinate-systems
embedded Bug 1539599 [wpt PR 16062] - Expand/ceil default object size in SVGImagePainter, a=testonly 2019-04-24 11:30:59 +01:00
extensibility
geometry
import
interact
linking Bug 1547619 - Fix :-moz-svg-use-shadow-tree-root pseudo-class. r=violet 2019-04-29 08:04:22 +00:00
painting
path
pservers Bug 1538332 [wpt PR 15953] - Allow degenerate SVG radial gradients, a=testonly 2019-04-24 11:18:52 +01:00
render/reftests
rendering/order
scripted
shapes
struct Bug 1537553 [wpt PR 15933] - Preserve explicit dimensions on <use>'d <symbol>, a=testonly 2019-04-24 11:18:27 +01:00
styling
svg-in-svg
text Bug 1536226 [wpt PR 15118] - WIP Add basic 'text-anchor' tests., a=testonly 2019-04-01 14:43:44 +01:00
types
historical.html
idlharness.window.js Bug 1532639 [wpt PR 15630] - Add <meta name=timeout content=long> to WPT in SlowTests, a=testonly 2019-04-24 11:19:30 +01:00
META.yml Bug 1536187 [wpt PR 14798] - Remove inactive reviewers, a=testonly 2019-04-01 14:43:38 +01:00
README.md

The import directory contains tests imported from the SVG 1.1 Second Edition test suite, with tests renamed to contain -manual in their name. These tests need review to verify that they are still correct for the latest version of SVG (which at the time of writing is SVG 2) and then need to be converted to reftests or testharness.js-based tests.

The SVG 1.1 test suite came with reference PNGs for each test, which, while not suitable as exact reftest reference files, at least give a rough indication of what the test should look like. For some tests, such as those involving filters, the test pass criteria are written with reference to the PNGs. When converting the tests to reftests or testharness.js-based tests, you might want to consult the reference PNG.

Tests should be placed in a directory named after the SVG 2 chapter name (for example in the shapes/ directory for Basic Shapes chapter tests). Scripted tests should be placed under a scripted/ subdirectory and reftests under a reftests/ subdirectory, within the chapter directory. Filenames for tests of DOM methods and properties should start with InterfaceName.methodOrPropertyName, such as types/scripted/SVGElement.ownerSVGElement-01.html.

Direct questions about the imported SVG 1.1 tests to Cameron McCormack.