-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Adding styles to the Separator block #25991
Comments
@aaronrobertshaw Hey Aaron I am just making you aware of this issue. As it would be nice to later on add some more styles to the Separator block. |
Thanks for looping me in on this one. It will be interesting to see what new styles can be added. |
I am digging through older issue and came across this one. What if we add padding into the Dimensions panel? Making it possible to have a thicker line... Seems like an easy adjustment to add. Then perhaps a corner radius to have a thicker line with curved corners. Then we can have a border line as well. Using the tools we have today we can get a more varied HR Separator line. |
Unfortunately, I don't think it is as simple as adopting something like padding. The block itself and some default themes have very different approaches to the separator. For example:
There are a lot more edge cases than those above and plenty of history in other issues or old PRs (e.g. #16928). Not that this is a solution, or even a satisfactory workaround, but it would be possible to get the thicker line and rounded corners mentioned via a group block and borders.
|
Is your feature request related to a problem? Please describe.
Existing styles which currently are located in the Separator block:
Describe the solution you'd like
It would be nice to have additional styles.
I have added Waves, Jagged and Loops to the mockup.
It creates a larger variation of decorations we can play with for the design.
Some of the inspiration came from here:
https://www.ecosia.org/images?q=various+line+types#id=88B94EC6E1CB8AC43E92FC497C666864E2718505
Overview issue: #16483
The text was updated successfully, but these errors were encountered: