Skip to content

Conversation

tylersticka
Copy link
Member

Overview

We lacked a default style for hr. This changes that. It uses the top border of footnote-group for basic appearance, but takes more color cues from the left comment border so that it will have slightly better contrast (and better compatibility with secondary themes). (I resisted the urge to style the footnote group to match because that feels like a visual distinction that does not necessarily warrant greater contrast.)

It also extends those styles to the WordPress "Separator" block.

Screenshots

Screen Shot 2021-11-08 at 10 32 54 AM

Screen Shot 2021-11-08 at 10 33 04 AM

Screen Shot 2021-11-08 at 10 33 18 AM

Screen Shot 2021-11-08 at 10 33 23 AM

Screen Shot 2021-11-08 at 10 33 30 AM


@changeset-bot
Copy link

changeset-bot bot commented Nov 8, 2021

🦋 Changeset detected

Latest commit: 6566904

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@cloudfour/patterns Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@netlify
Copy link

netlify bot commented Nov 8, 2021

✔️ Deploy Preview for cloudfour-patterns ready!

🔨 Explore the source changes: 6566904

🔍 Inspect the deploy log: https://app.netlify.com/sites/cloudfour-patterns/deploys/6189a3454205690008f8f6f1

😎 Browse the preview: https://deploy-preview-1575--cloudfour-patterns.netlify.app

@tylersticka tylersticka marked this pull request as ready for review November 8, 2021 18:44
@tylersticka tylersticka requested review from a team November 8, 2021 18:44
spaceninja
spaceninja previously approved these changes Nov 8, 2021
hr {
border-color: currentColor;
border-style: solid;
border-width: math.div(size.$edge-medium, 2) 0;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I trust you have a good reason, so I'm still going to approve, but perhaps you could add a comment here explaining why this is set to 1/2 of $edge-medium, rather than just using $edge-small?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@spaceninja I've pushed up an additional comment that I hope explains it better.

Comment on lines +293 to +294
margin-left: auto;
margin-right: auto;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is our browser support good enough to use margin-inline?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@spaceninja Good question. It looks like we currently have 104 occurrences of traditional margin properties in the project already, so I think I'll create a separate issue about investigating this. Maybe also look into a linting error depending on where that lands?

Copy link
Member Author

@tylersticka tylersticka Nov 8, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tylersticka tylersticka merged commit c51b164 into v-next Nov 9, 2021
@tylersticka tylersticka deleted the feature/hr branch November 9, 2021 17:56
@github-actions github-actions bot mentioned this pull request Nov 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Style <hr>s
2 participants