Styling in Gutenberg is missing in 6.4

[Rvervuurt]

The standard-styling of Gutenberg text areas has been removed in 6.4:

The top two lines in this view are the title (normally huge) and the 2nd one is an h2-element:

When inspecting the element, it seems reset.css isn't properly applied:

If I add !important to the strike-through styles, it works properly:

Seems to be a CSS specificity-error.

[Rvervuurt]

Update: When changing to twentytwentyfour, some other styling is applied:

Reverting to 6.3.2 fixes the problem:

Is this something I have to fix in my custom theme? Or what is happening here?

[jorbin]

While the issue is different, I wonder if the root cause is the same as #59847. Can you test the changeset there?

[geoffreybr]

We face the same issue and I tried to apply the changes from PR 5644 but it doesn't solve it.

Actually it comes from a change in wp-includes/css/dist/block-library/reset.css where all rules were prefixed with html selector prior to 6.4.

The change was introduced by this commit:
​https://github.com/WordPress/gutenberg/commit/b18a270ae4b5d71cc0d880d40d21b5163686cd92?diff=unified#diff-bda8e417e9cfc8724167f4c82aab1d0d205245c51360a8afa4bba99ba078e6db

[jorbin]

Thanks @geoffreybr for investigating.

Tagging @ellatrix who committed the change referenced.

[hellofromTonya]

The same ​Gutenberg PR referenced in this ticket has been referenced in ​Gutenberg issue 56293. I've reopened that Gutenberg issue and cross-linked it to this Trac ticket. That particular issue received a ​fix in relation to scope without specificity, which was merged earlier today into Gutenberg.

These 2 issues appear to be related to the ​same original Gutenberg commit and potentially other Trac reports of specificity.

Moving into 6.4.2 for monitoring / tracking. The work though will be done upstream in Gutenberg and when fixed, the corresponding fixes will get published in package updates and Core's package.json updated.

[jorbin]

Based on lack of forward movement, I'm bumping this out of 6.4.3

[swissspidy]

Surely this must be fixed now with all the package updates in 6.5?

Can anyone confirm?