Thinking about the original issue, if it was really intentional for center to be default, and how we'd support "unsetting" that value, I think if that was something we'd want to support, we could do so by setting the alignment to null instead of undefined. As undefined, I think it's sensible that the default value take effect.

This, of course, is a non-issue after these changes.

Totally unrelated to the changes here, but the alignment implementation doesn't work so well on lots of themes, where margin: 0 auto; on an element which is full-width already doesn't do anything (i.e. doesn't appear to be centered). But the class is there.

Failing test was legitimate. => assignment alignment needed to be updated. Pushed change in c1fabd2.

Thank you so much for the correction and merge @aduth ❤️

@aduth Any idea why we don't use flex to center the list items instead of margin: 0 auto; which mostly doesn't work.

That would, of course, require us to wrap the list up with a div wrapper. Let me know if you want me to submit PRs with that. Thanks ❤️

@nfmohit-wpmudev

A few things:

• Apparently we don't add anything in the editor to reflect center alignment? That might be a good first step 😄
• There's already a fair bit of inconsistency in alignment options across blocks, observed at Unify the block toolbar for all text blocks #3785 . The first point and this issue could be jointly remedied by using the align supports
• The margin: 0 auto; is the implementation of .aligncenter, which predates Gutenberg. I imagine the reasoning for this may be broader browser support: While wp-admin supports only IE11 and newer, we need to be more careful about the content we produce. I realize there's some hypocrisy here in that the Columns block uses Flex. Mentioning less as a reason to "not do it", but more as context for why it may not have been used.

Got it, thank you so much for the explanation @aduth ❤️