-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Border type feedback #99
Comments
Hi, what would be the recommended way to store border-radius? |
The more I use that, the more I think, "border" is the wrong word, instead "stroke" is more appropriate:
Or: A stroke can be a border, but a border cannot be a stroke. And to add what @tlouisse said: A ruler (= a line) cannot have a radius. So, there is:
1 When location is omitted, border is applied on all sides, then border equals stroke |
I don't know if this is the correct place to bring this up, but I've seen in a handful of designs (mostly documented in Figma) that some elements use "inside" or "outside" aligned borders, for example to create a focus "border" around a button. I do know that it most technologies, this effect does not fall into the border property (For example in CSS you would set Is this "alignment" of the border being considered in any place on the standard? |
@gossi +1 |
Is the border composite type fit for purpose? Does it need more sub-values to account for features like outset, border images, multiple borders, etc. that some platforms an design tools have?
Please share your feedback, thoughts and ideas in this issue.
The text was updated successfully, but these errors were encountered: