I tested this and it worked great!

Let's merge this, but keep in mind that we may want to reevaluate the background color options for all these text blocks and just use the Group block to provide that.

But keep in mind that we may want to reevaluate the background color options for all these text blocks

Do we have a decision here, because I'd rather not introduce something that is going to be removed (it's always hard to remove things when they become APIs)

Do we have a decision here?

Yes, we're going to keep this in. A decision is made to keep background color on most (if not all) text blocks. #8171 (comment)

Let's merge it.

Thank you for the reviews @youknowriad, @mapk 👍

We could use an e2e test.

I will follow up with an end 2 end test for this functionality.

I wonder how much of this code could be reused across blocks.

We already have a big amount of code reusability, by using shared components for the UI, withColors for the logic, and shared functions. But I agree it is something we could try to improve further. The main decision we would need to do would be the way this reusability would work, the simplest option would be a supports flag for color, but in previous discussions, there was no clear agreement if we should continue investing in support options.

We really need this for all block controls (lists, paragraphs etc). Anything that can be used on a group block with a coloured background could cause readability issues and so the text colour will need to be changeable.

That's the next step here, @BinaryMoon. We want to add text color options to all text blocks.

The .has-text-color class is missing. It only shows the .has-xxx-color class.

Heading background color was removed:
#15814

With the thought that "The idea being that backgrounds should be higher-level (group block)."