Categories block doesn't inherit css from style.css on the Editor

[SGr33n]

Description

Hi!
Defining a custom style for the categories core block doesn't affect that style on the editor.
The style works, on the other hand, on the page list block (pretty similar to the categories one).

Step-by-step reproduction instructions

Add a categories list block and a page list block.
Add the following code on your styles.css

.wp-block-categories-list,
.wp-block-page-list {
	list-style-type: none;
	padding-left: 0;
}

both are working on the frontend, while only the page list block is getting the correct style.

This looks a problem on the Editor's class names:
block-editor-block-list__block wp-block wp-block-page-list on the block pages list.
wp-block-categories__list wp-block-categories__list-level-0 on the categories list block.

the second one should probably be:
block-editor-block-list__block wp-block wp-block-categories-list

Screenshots, screen recording, code snippet

No response

Environment info

WordPress: 6.0.2
Gutenmberg: latest trunk
Theme: TwentyTwenty-two

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

[carolinan]

Hi!
Style.css in themes is not added to the editor by default. The theme needs to use an editor style. I mention this because it is not clear from the issue description, how the style.css is added. Sorry if this is obvious.

[SGr33n]

It's on twentytwenty-two, on the theme main stylesheet, it's correctly added to the Gutenberg editor:

Frontend:

Gutenberg:

[carolinan]

Are you able to test if your CSS works with this PR? #43666

[SGr33n]

Sorry i forgot to mention that this test was made on the latest Gutenberg trunk, so this PR should already be in.

[t-hamano]

@SGr33n
Thank you for submitting the Issue.
Issue #43666 was not merged at the time you commented, so it was not reflected in the latest trunk.
I have just merged it and would like to close this issue.

If you pull the latest trunk, you should see that this issue has been resolved.
If the issue has not been resolved, please do not worry about it and reopen.

[SGr33n]

Thanks @t-hamano and @carolinan!

[SGr33n]

I can confirm, #43666 solved this.
Thanks!