Skip to content

Conversation

@adamwathan
Copy link
Member

Currently margins are removed in the list-reset class.

We remove margins by default on all kinds of other elements, so it seems reasonable to me to remove them by default on lists too, leaving list-reset to only handle removing the list style and the left padding.

Without this, lists will have some non-standard margin on the top and bottom by default that uses a value from outside of Tailwind's spacing config, which seems like an unnecessary inconsistency.

I'm also considering changing list-reset to list-style-none and putting the onus on the user to remove the padding, but also happy to make that a separate PR, and still not entirely convinced on it anyways.


ol,
ul {
margin: 0;
Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Member Author

Choose a reason for hiding this comment

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

I considered that but those selectors are in alphabetical order, and keeping things in alphabetical order would separate ol and ul from each other 🤔 So opted to just keep it as an explicit rule, although I'm also happy to move it there if you think that's better.

Copy link
Member

Choose a reason for hiding this comment

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

Nah I don't care that much. My only thinking was trying to keep normalize as standard as possible, and then only making tweaks to our basecss fork.

But maybe we're already making other (non-comment) changes to normalize?

Copy link
Contributor

Choose a reason for hiding this comment

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

It is in the SUIT CSS Base fork, not in Normalize. I’m confused?

@adamwathan adamwathan merged commit cbe89ea into 0.3 Nov 28, 2017
@adamwathan adamwathan deleted the remove-list-margin branch November 28, 2017 14:29
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.

4 participants