- From: jsnkuhn via GitHub <noreply@w3.org>
- Date: Wed, 29 Oct 2025 23:18:00 +0000
- To: public-css-archive@w3.org
In the all `bevel` rhombus example personally I would not be expecting the beveled line join by default. Just had a look through the use case example thread (https://github.com/w3c/csswg-drafts/issues/6980) and I did not find any example of a bevel mitered join on an outer "border". If you render the beveled miter by default and people _don't_ want it there's nothing they can really do to work around it. If someone _does_ want the bevel joint and it's not there they could use for example `clip-path: inset(-16px);` to cut off the bits they don't want. Maybe this needs it's own CSS a property? SVG has a `stroke-linejoin` property to control this. The default is `miter` not `bevel` https://developer.mozilla.org/en-US/docs/Web/SVG/Reference/Attribute/stroke-linejoin#usage_context Canvas has `linejoint`. The default is also `miter` not `bevel` https://developer.mozilla.org/en-US/docs/Web/API/CanvasRenderingContext2D/lineJoin#value -- GitHub Notification of comment by jsnkuhn Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13037#issuecomment-3464916800 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 October 2025 23:18:01 UTC