Index: LayoutTests/svg/custom/invalid-fill.svg |
diff --git a/LayoutTests/svg/custom/invalid-fill.svg b/LayoutTests/svg/custom/invalid-fill.svg |
deleted file mode 100644 |
index aea3eaa78497c6e8c2cff30638f570495d082be0..0000000000000000000000000000000000000000 |
--- a/LayoutTests/svg/custom/invalid-fill.svg |
+++ /dev/null |
@@ -1,14 +0,0 @@ |
-<?xml version="1.0" encoding="UTF-8"?> |
-<svg xmlns="http://www.w3.org/2000/svg"> |
- <g fill="orange"> |
- <rect width="100" height="100" fill="red"/> |
- <rect width="100" height="100" fill="url(#notthere)"/> |
- <g fill="black"> |
- <text x="10" y="130">The above rect should be ORANGE.</text> |
- <text x="10" y="150">SVG 1.1 FULL says there should be a "highly perceivable error" message when an invalid fill is used.</text> |
- <text x="10" y="170">Browsers don't display such an error, instead use some sort of fill-fallback.</text> |
- <text x="10" y="190">If there's an non-existent uri, but no fallback specified, the fill of the object is inherited from parent object.</text> |
- <text x="10" y="210">This has recently been changed in SVG 1.1 2nd edition. Our result matches Opera now.</text> |
- </g> |
- </g> |
-</svg> |