Skip to content

Browsers do not accept stroke-linejoin 'miter-clip' or 'arcs' #592

Closed

Description

@ewilligers

https://svgwg.org/svg2-draft/painting.html#LineJoin

Name: stroke-linejoin
Value: miter | miter-clip | round | bevel | arcs

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?

Activity

  1. self-assigned this
    on Dec 2, 2018
  2. css-meeting-bot commented on Dec 3, 2018

    @css-meeting-bot
    Member

    The SVG Working Group just discussed At-risk status of new stroke-linejoin keywords, and agreed to the following:

    • RESOLVED: Mark new stroke-linejoin keywords as at risk.
    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.
  3. dirkschulze commented on Dec 4, 2018

    @dirkschulze
    Contributor

    @ericwilligers Could you publish the tests to web-platform-tests please?

  4. ewilligers commented on Dec 4, 2018

    @ewilligers
    ContributorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions