-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Removing wrapper div from the categories block #9798
Conversation
Previously, the categories block was rendered inside a div, while other list-based blocks (archives, latest posts, list, etc.) were not. This update removes the div wrapper for consistency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for me. Technically it's a breaking change for anyone styling things if they happened to rely on it being a div
, but that seems silly anyway 😄 . Dunno how we tend to handle that with markup, but the change itself looks good.
While we're updating the Categories block markup, shouldn't it also use an |
Thanks, @tofumatt — I agree that this seems like it'd be a very small fraction of themes. If anything, I've mostly heard from theme authors who dislike that these are inconsistent. 😄 So I think we're good to go.
@ZebulanStanphill: |
@kjellr |
@ZebulanStanphill I think the difference here is that if the order of the categories were to change, there would be no change in meaning. However, changing the order of comments would change the way they're interpreted, since comments may reply to each other or provide context as a discussion continues.
(Emphasis is mine) |
Fixes #9411
Previously, the categories block was rendered inside a div, while other list-based blocks (archives, latest posts, list, etc.) were not. This update removes the div wrapper for consistency.
Previously, this block would render like this:
But this change updates that to:
We still need the wrapper div if this is shown as a dropdown, so this doesn't effect that. Seems like a simple change, and doesn't seem to require any css updates.