- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Jul 2022 16:33:15 +0000
- To: public-css-archive@w3.org
> # Border-path > * `border-path` defines a path using syntax derived from `clip-path` and `shape-outside`. Namely, a [CSS shape](https://drafts.csswg.org/css-shapes/). > * `clip-path` can have a value of `border-path`, which would cause it to use the path defined in the `border-path` property. > * Any non-initial value for `border-path` will set the computed value of `clip path` to either `border-path` or `none`, depending on if `overflow` is `visible` or not. > * `shape-outside` can have a value of `border-path`, which would cause it to use the path defined in the `border-path` property, offset by the value of `margin-top` or `margin-block-start`. This is only visibly noticeable if the element is floated. Interesting, I like the direction. I originally thought you'd need to use CSS variables for them to be the same. I wonder though, why could border-path be a reference value, and not shape-outside or clip-path? (i.e.. why `clip-path: border-path` and not `border-path: clip-path`)? What makes that one the "root" path? I also wonder how it should interact with `border-radius`. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5881#issuecomment-1176434960 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 July 2022 16:33:16 UTC