Browsers do not accept stroke-linejoin 'miter-clip' or 'arcs' #592
Comments
ewilligers
pushed a commit
to ewilligers/web-platform-tests
that referenced
this issue
Nov 17, 2018
Test that properties support the full grammar. https://svgwg.org/svg2-draft/painting.html The tests highlight a number of spec and implementation issues:- Spec issues: Blink/Edge/Firefox/Safari do not accept percentage fill-opacity/stroke-opacity w3c/svgwg#403 (comment) Browsers do not accept stroke-linejoin 'miter-clip' or 'arcs' w3c/svgwg#592 Browsers accept numeric stroke-dashoffset and stroke-width w3c/svgwg#534 Browser bugs: Blink image-rendering does not accept 'optimizespeed' or 'optimizequality' https://bugs.chromium.org/p/chromium/issues/detail?id=901669 Firefox rejects stroke-miterlimit less than 1 https://bugzilla.mozilla.org/show_bug.cgi?id=1508028 Edge serializes fill/stroke url() without quoting the url string. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/16900961/ Edge accepts misformed numbers fill-opacity: 1.; stroke-miterlimit: 1.; stroke-opacity: 1.; https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656838/ Edge accepts negative stroke-dasharray Edge does not accept calc in stroke-dasharray https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656979/ Edge accepts negative stroke-width values https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656907/ Safari accepts negative stroke-width https://bugs.webkit.org/show_bug.cgi?id=191804 Safari serializes color-interpolation, color-rendering, image-rendering, shape-rendering, text-rendering in mixed case https://bugs.webkit.org/show_bug.cgi?id=190685 Edge serializes paint-order 'normal' as 'fill', unlike other browsers. Firefox does not use shortest paint-order serialization, instead it uses 2 keywords when 1 would suffice Browsers yet to implement properties: Firefox does not support color-rendering Edge does not support color-interpolation/color-rendering/image-rendering/shape-rendering/text-rendering Note: When implementing, the keywords should serialize in lower case. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19328562/ Browsers yet to implement keywords: Blink/Edge/Safari do not accept fill/stroke 'context-fill' or 'context-stroke' Firefox does support the keywords: https://jsfiddle.net/ericwilligers/8bhyafe1/
ewilligers
pushed a commit
to ewilligers/web-platform-tests
that referenced
this issue
Nov 17, 2018
Test that properties support the full grammar. https://svgwg.org/svg2-draft/painting.html The tests highlight a number of spec and implementation issues:- Spec issues: Blink/Edge/Firefox/Safari do not accept percentage fill-opacity/stroke-opacity w3c/svgwg#403 (comment) Browsers do not accept stroke-linejoin 'miter-clip' or 'arcs' w3c/svgwg#592 Browsers accept numeric stroke-dashoffset and stroke-width w3c/svgwg#534 Browser bugs: Blink image-rendering does not accept 'optimizespeed' or 'optimizequality' https://bugs.chromium.org/p/chromium/issues/detail?id=901669 Firefox rejects stroke-miterlimit less than 1 https://bugzilla.mozilla.org/show_bug.cgi?id=1508028 Edge serializes fill/stroke url() without quoting the url string. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/16900961/ Edge accepts misformed numbers fill-opacity: 1.; stroke-miterlimit: 1.; stroke-opacity: 1.; https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656838/ Edge accepts negative stroke-dasharray Edge does not accept calc in stroke-dasharray https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656979/ Edge accepts negative stroke-width values https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656907/ Safari accepts negative stroke-width https://bugs.webkit.org/show_bug.cgi?id=191804 Safari serializes color-interpolation, color-rendering, image-rendering, shape-rendering, text-rendering in mixed case https://bugs.webkit.org/show_bug.cgi?id=190685 Edge serializes paint-order 'normal' as 'fill', unlike other browsers. Firefox does not use shortest paint-order serialization, instead it uses 2 keywords when 1 would suffice Browsers yet to implement properties: Firefox does not support color-rendering Edge does not support color-interpolation/color-rendering/image-rendering/shape-rendering/text-rendering Note: When implementing, the keywords should serialize in lower case. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19328562/ Browsers yet to implement keywords: Blink/Edge/Safari do not accept fill/stroke 'context-fill' or 'context-stroke' Firefox does support the keywords: https://jsfiddle.net/ericwilligers/8bhyafe1/
ewilligers
pushed a commit
to ewilligers/web-platform-tests
that referenced
this issue
Nov 21, 2018
Test that properties support the full grammar. https://svgwg.org/svg2-draft/painting.html The tests highlight a number of spec and implementation issues:- Spec issues: Blink/Edge/Firefox/Safari do not accept percentage fill-opacity/stroke-opacity w3c/svgwg#403 (comment) Browsers do not accept stroke-linejoin 'miter-clip' or 'arcs' w3c/svgwg#592 Browsers accept numeric stroke-dashoffset and stroke-width w3c/svgwg#534 Browser bugs: Blink image-rendering does not accept 'optimizespeed' or 'optimizequality' https://bugs.chromium.org/p/chromium/issues/detail?id=901669 Firefox rejects stroke-miterlimit less than 1 https://bugzilla.mozilla.org/show_bug.cgi?id=1508028 Edge serializes fill/stroke url() without quoting the url string. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/16900961/ Edge accepts misformed numbers fill-opacity: 1.; stroke-miterlimit: 1.; stroke-opacity: 1.; https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656838/ Edge accepts negative stroke-dasharray Edge does not accept calc in stroke-dasharray https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656979/ Edge accepts negative stroke-width values https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656907/ Safari accepts negative stroke-width https://bugs.webkit.org/show_bug.cgi?id=191804 Safari serializes color-interpolation, color-rendering, image-rendering, shape-rendering, text-rendering in mixed case https://bugs.webkit.org/show_bug.cgi?id=190685 Edge serializes paint-order 'normal' as 'fill', unlike other browsers. Firefox does not use shortest paint-order serialization, instead it uses 2 keywords when 1 would suffice Browsers yet to implement properties: Firefox does not support color-rendering Edge does not support color-interpolation/color-rendering/image-rendering/shape-rendering/text-rendering Note: When implementing, the keywords should serialize in lower case. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19328562/ Browsers yet to implement keywords: Blink/Edge/Safari do not accept fill/stroke 'context-fill' or 'context-stroke' Firefox does support the keywords: https://jsfiddle.net/ericwilligers/8bhyafe1/
ewilligers
added a commit
to web-platform-tests/wpt
that referenced
this issue
Nov 21, 2018
Test that properties support the full grammar. https://svgwg.org/svg2-draft/painting.html The tests highlight a number of spec and implementation issues:- Spec issues: Blink/Edge/Firefox/Safari do not accept percentage fill-opacity/stroke-opacity w3c/svgwg#403 (comment) Browsers do not accept stroke-linejoin 'miter-clip' or 'arcs' w3c/svgwg#592 Browsers accept numeric stroke-dashoffset and stroke-width w3c/svgwg#534 Browser bugs: Blink image-rendering does not accept 'optimizespeed' or 'optimizequality' https://bugs.chromium.org/p/chromium/issues/detail?id=901669 Firefox rejects stroke-miterlimit less than 1 https://bugzilla.mozilla.org/show_bug.cgi?id=1508028 Edge serializes fill/stroke url() without quoting the url string. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/16900961/ Edge accepts misformed numbers fill-opacity: 1.; stroke-miterlimit: 1.; stroke-opacity: 1.; https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656838/ Edge accepts negative stroke-dasharray Edge does not accept calc in stroke-dasharray https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656979/ Edge accepts negative stroke-width values https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656907/ Safari accepts negative stroke-width https://bugs.webkit.org/show_bug.cgi?id=191804 Safari serializes color-interpolation, color-rendering, image-rendering, shape-rendering, text-rendering in mixed case https://bugs.webkit.org/show_bug.cgi?id=190685 Edge serializes paint-order 'normal' as 'fill', unlike other browsers. Firefox does not use shortest paint-order serialization, instead it uses 2 keywords when 1 would suffice Browsers yet to implement properties: Firefox does not support color-rendering Edge does not support color-interpolation/color-rendering/image-rendering/shape-rendering/text-rendering Note: When implementing, the keywords should serialize in lower case. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19328562/ Browsers yet to implement keywords: Blink/Edge/Safari do not accept fill/stroke 'context-fill' or 'context-stroke' Firefox does support the keywords: https://jsfiddle.net/ericwilligers/8bhyafe1/
moz-v2v-gh
pushed a commit
to mozilla/gecko-dev
that referenced
this issue
Nov 29, 2018
Automatic update from web-platform-testsSVG Painting: property parsing (#14114) Test that properties support the full grammar. https://svgwg.org/svg2-draft/painting.html The tests highlight a number of spec and implementation issues:- Spec issues: Blink/Edge/Firefox/Safari do not accept percentage fill-opacity/stroke-opacity w3c/svgwg#403 (comment) Browsers do not accept stroke-linejoin 'miter-clip' or 'arcs' w3c/svgwg#592 Browsers accept numeric stroke-dashoffset and stroke-width w3c/svgwg#534 Browser bugs: Blink image-rendering does not accept 'optimizespeed' or 'optimizequality' https://bugs.chromium.org/p/chromium/issues/detail?id=901669 Firefox rejects stroke-miterlimit less than 1 https://bugzilla.mozilla.org/show_bug.cgi?id=1508028 Edge serializes fill/stroke url() without quoting the url string. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/16900961/ Edge accepts misformed numbers fill-opacity: 1.; stroke-miterlimit: 1.; stroke-opacity: 1.; https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656838/ Edge accepts negative stroke-dasharray Edge does not accept calc in stroke-dasharray https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656979/ Edge accepts negative stroke-width values https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656907/ Safari accepts negative stroke-width https://bugs.webkit.org/show_bug.cgi?id=191804 Safari serializes color-interpolation, color-rendering, image-rendering, shape-rendering, text-rendering in mixed case https://bugs.webkit.org/show_bug.cgi?id=190685 Edge serializes paint-order 'normal' as 'fill', unlike other browsers. Firefox does not use shortest paint-order serialization, instead it uses 2 keywords when 1 would suffice Browsers yet to implement properties: Firefox does not support color-rendering Edge does not support color-interpolation/color-rendering/image-rendering/shape-rendering/text-rendering Note: When implementing, the keywords should serialize in lower case. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19328562/ Browsers yet to implement keywords: Blink/Edge/Safari do not accept fill/stroke 'context-fill' or 'context-stroke' Firefox does support the keywords: https://jsfiddle.net/ericwilligers/8bhyafe1/ -- wpt-commits: e50224228f7629af05d08a50f36afbacfbd0158e wpt-pr: 14114
xeonchen
pushed a commit
to xeonchen/gecko
that referenced
this issue
Nov 29, 2018
Automatic update from web-platform-testsSVG Painting: property parsing (#14114) Test that properties support the full grammar. https://svgwg.org/svg2-draft/painting.html The tests highlight a number of spec and implementation issues:- Spec issues: Blink/Edge/Firefox/Safari do not accept percentage fill-opacity/stroke-opacity w3c/svgwg#403 (comment) Browsers do not accept stroke-linejoin 'miter-clip' or 'arcs' w3c/svgwg#592 Browsers accept numeric stroke-dashoffset and stroke-width w3c/svgwg#534 Browser bugs: Blink image-rendering does not accept 'optimizespeed' or 'optimizequality' https://bugs.chromium.org/p/chromium/issues/detail?id=901669 Firefox rejects stroke-miterlimit less than 1 https://bugzilla.mozilla.org/show_bug.cgi?id=1508028 Edge serializes fill/stroke url() without quoting the url string. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/16900961/ Edge accepts misformed numbers fill-opacity: 1.; stroke-miterlimit: 1.; stroke-opacity: 1.; https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656838/ Edge accepts negative stroke-dasharray Edge does not accept calc in stroke-dasharray https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656979/ Edge accepts negative stroke-width values https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656907/ Safari accepts negative stroke-width https://bugs.webkit.org/show_bug.cgi?id=191804 Safari serializes color-interpolation, color-rendering, image-rendering, shape-rendering, text-rendering in mixed case https://bugs.webkit.org/show_bug.cgi?id=190685 Edge serializes paint-order 'normal' as 'fill', unlike other browsers. Firefox does not use shortest paint-order serialization, instead it uses 2 keywords when 1 would suffice Browsers yet to implement properties: Firefox does not support color-rendering Edge does not support color-interpolation/color-rendering/image-rendering/shape-rendering/text-rendering Note: When implementing, the keywords should serialize in lower case. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19328562/ Browsers yet to implement keywords: Blink/Edge/Safari do not accept fill/stroke 'context-fill' or 'context-stroke' Firefox does support the keywords: https://jsfiddle.net/ericwilligers/8bhyafe1/ -- wpt-commits: e50224228f7629af05d08a50f36afbacfbd0158e wpt-pr: 14114
|
The SVG Working Group just discussed
The full IRC log of that discussion<AmeliaBR> Topic: At-risk status of new stroke-linejoin keywords<AmeliaBR> github: https://github.com//issues/592 <AmeliaBR> Chris: These really do have to be at-risk. They are new features, and we have no browser implementations. <AmeliaBR> Tav: There are implementations in Inkscape, using a modified version of Cairo. They are also recreated with our live path effects. <AmeliaBR> Dirk: You said you implemented with Cairo? <AmeliaBR> Tav: In a modified version. Not in the public library. <AmeliaBR> ... we also have a similar thing in the path effects, which uses custom attributes that are then exported as standard SVG path. It's very popular among artists. <AmeliaBR> Dirk: Any objections to marking at-risk? <AmeliaBR> RESOLVED: Mark new stroke-linejoin keywords as at risk. <AmeliaBR> Eric: Do we have any feedback from implementers? Is there any interest of implementing? <AmeliaBR> Myles: Same issue as before. Not a lot of feedback from authors yet. I don't think there are technical obstacles. <AmeliaBR> Chris: Again, I think we need more worked examples and education to get people excited about them. |
|
@ericwilligers Could you publish the tests to web-platform-tests please? |
|
The parsing test shows which values browsers accept. Each browser passes 3 of the 5 tests, as they accept 3 of the 5 keywords. I skipped the 2 unimplemented values in the computed values test. I can add them. |
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified
that referenced
this issue
Oct 3, 2019
Automatic update from web-platform-testsSVG Painting: property parsing (#14114) Test that properties support the full grammar. https://svgwg.org/svg2-draft/painting.html The tests highlight a number of spec and implementation issues:- Spec issues: Blink/Edge/Firefox/Safari do not accept percentage fill-opacity/stroke-opacity w3c/svgwg#403 (comment) Browsers do not accept stroke-linejoin 'miter-clip' or 'arcs' w3c/svgwg#592 Browsers accept numeric stroke-dashoffset and stroke-width w3c/svgwg#534 Browser bugs: Blink image-rendering does not accept 'optimizespeed' or 'optimizequality' https://bugs.chromium.org/p/chromium/issues/detail?id=901669 Firefox rejects stroke-miterlimit less than 1 https://bugzilla.mozilla.org/show_bug.cgi?id=1508028 Edge serializes fill/stroke url() without quoting the url string. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/16900961/ Edge accepts misformed numbers fill-opacity: 1.; stroke-miterlimit: 1.; stroke-opacity: 1.; https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656838/ Edge accepts negative stroke-dasharray Edge does not accept calc in stroke-dasharray https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656979/ Edge accepts negative stroke-width values https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656907/ Safari accepts negative stroke-width https://bugs.webkit.org/show_bug.cgi?id=191804 Safari serializes color-interpolation, color-rendering, image-rendering, shape-rendering, text-rendering in mixed case https://bugs.webkit.org/show_bug.cgi?id=190685 Edge serializes paint-order 'normal' as 'fill', unlike other browsers. Firefox does not use shortest paint-order serialization, instead it uses 2 keywords when 1 would suffice Browsers yet to implement properties: Firefox does not support color-rendering Edge does not support color-interpolation/color-rendering/image-rendering/shape-rendering/text-rendering Note: When implementing, the keywords should serialize in lower case. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19328562/ Browsers yet to implement keywords: Blink/Edge/Safari do not accept fill/stroke 'context-fill' or 'context-stroke' Firefox does support the keywords: https://jsfiddle.net/ericwilligers/8bhyafe1/ -- wpt-commits: e50224228f7629af05d08a50f36afbacfbd0158e wpt-pr: 14114 UltraBlame original commit: 0818f88fb0cfb9216e37e2556fe85446e3e388e8
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-comments-removed
that referenced
this issue
Oct 3, 2019
Automatic update from web-platform-testsSVG Painting: property parsing (#14114) Test that properties support the full grammar. https://svgwg.org/svg2-draft/painting.html The tests highlight a number of spec and implementation issues:- Spec issues: Blink/Edge/Firefox/Safari do not accept percentage fill-opacity/stroke-opacity w3c/svgwg#403 (comment) Browsers do not accept stroke-linejoin 'miter-clip' or 'arcs' w3c/svgwg#592 Browsers accept numeric stroke-dashoffset and stroke-width w3c/svgwg#534 Browser bugs: Blink image-rendering does not accept 'optimizespeed' or 'optimizequality' https://bugs.chromium.org/p/chromium/issues/detail?id=901669 Firefox rejects stroke-miterlimit less than 1 https://bugzilla.mozilla.org/show_bug.cgi?id=1508028 Edge serializes fill/stroke url() without quoting the url string. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/16900961/ Edge accepts misformed numbers fill-opacity: 1.; stroke-miterlimit: 1.; stroke-opacity: 1.; https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656838/ Edge accepts negative stroke-dasharray Edge does not accept calc in stroke-dasharray https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656979/ Edge accepts negative stroke-width values https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656907/ Safari accepts negative stroke-width https://bugs.webkit.org/show_bug.cgi?id=191804 Safari serializes color-interpolation, color-rendering, image-rendering, shape-rendering, text-rendering in mixed case https://bugs.webkit.org/show_bug.cgi?id=190685 Edge serializes paint-order 'normal' as 'fill', unlike other browsers. Firefox does not use shortest paint-order serialization, instead it uses 2 keywords when 1 would suffice Browsers yet to implement properties: Firefox does not support color-rendering Edge does not support color-interpolation/color-rendering/image-rendering/shape-rendering/text-rendering Note: When implementing, the keywords should serialize in lower case. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19328562/ Browsers yet to implement keywords: Blink/Edge/Safari do not accept fill/stroke 'context-fill' or 'context-stroke' Firefox does support the keywords: https://jsfiddle.net/ericwilligers/8bhyafe1/ -- wpt-commits: e50224228f7629af05d08a50f36afbacfbd0158e wpt-pr: 14114 UltraBlame original commit: 0818f88fb0cfb9216e37e2556fe85446e3e388e8
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified-and-comments-removed
that referenced
this issue
Oct 3, 2019
Automatic update from web-platform-testsSVG Painting: property parsing (#14114) Test that properties support the full grammar. https://svgwg.org/svg2-draft/painting.html The tests highlight a number of spec and implementation issues:- Spec issues: Blink/Edge/Firefox/Safari do not accept percentage fill-opacity/stroke-opacity w3c/svgwg#403 (comment) Browsers do not accept stroke-linejoin 'miter-clip' or 'arcs' w3c/svgwg#592 Browsers accept numeric stroke-dashoffset and stroke-width w3c/svgwg#534 Browser bugs: Blink image-rendering does not accept 'optimizespeed' or 'optimizequality' https://bugs.chromium.org/p/chromium/issues/detail?id=901669 Firefox rejects stroke-miterlimit less than 1 https://bugzilla.mozilla.org/show_bug.cgi?id=1508028 Edge serializes fill/stroke url() without quoting the url string. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/16900961/ Edge accepts misformed numbers fill-opacity: 1.; stroke-miterlimit: 1.; stroke-opacity: 1.; https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656838/ Edge accepts negative stroke-dasharray Edge does not accept calc in stroke-dasharray https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656979/ Edge accepts negative stroke-width values https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19656907/ Safari accepts negative stroke-width https://bugs.webkit.org/show_bug.cgi?id=191804 Safari serializes color-interpolation, color-rendering, image-rendering, shape-rendering, text-rendering in mixed case https://bugs.webkit.org/show_bug.cgi?id=190685 Edge serializes paint-order 'normal' as 'fill', unlike other browsers. Firefox does not use shortest paint-order serialization, instead it uses 2 keywords when 1 would suffice Browsers yet to implement properties: Firefox does not support color-rendering Edge does not support color-interpolation/color-rendering/image-rendering/shape-rendering/text-rendering Note: When implementing, the keywords should serialize in lower case. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/19328562/ Browsers yet to implement keywords: Blink/Edge/Safari do not accept fill/stroke 'context-fill' or 'context-stroke' Firefox does support the keywords: https://jsfiddle.net/ericwilligers/8bhyafe1/ -- wpt-commits: e50224228f7629af05d08a50f36afbacfbd0158e wpt-pr: 14114 UltraBlame original commit: 0818f88fb0cfb9216e37e2556fe85446e3e388e8
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://svgwg.org/svg2-draft/painting.html#LineJoin
Blink/Edge/Firefox/Safari accept three of these values, but reject 'miter-clip' and 'arcs'
Test page: https://jsfiddle.net/ericwilligers/d65zk84s/
Should these values be marked at risk for SVG 2.0?
The text was updated successfully, but these errors were encountered: