Twenty Twenty Two: Pullquote block: Font change not properly displayed

[nithins53]

In the Twenty Twenty Two theme, when we change the size of the text in the pullquote block, it is not properly displayed in the editor.

Steps to replicate:
1.Activate twenty twenty two theme

2. Insert pullquote block
3. Insert text and change font size

For more information, screen recording link is attached below.

​https://www.loom.com/share/a1c88a8de95440a89cf8cfb53239643b

Thank You.

[devtanbir]

after applying this solution the issue is resolved.

[nithins53]

@devtanbir Thank you for the patch it works. Have you tested it on any other WordPress version?

[devtanbir]

@nithins53, I tested in version 6.0

[nithins53]

Replying to devtanbir:

@nithins53, I tested in version 6.0

Can you also test in on version 5.9 and report? I will also report after testing.

[devtanbir]

Replying to nithins53:

Replying to devtanbir:

@nithins53, I tested in version 6.0

Can you also test in on version 5.9 and report? I will also report after testing.

Again, I tested in version 5.9. Its works properly.

[nithins53]

Replying to devtanbir:

Replying to nithins53:

Replying to devtanbir:

@nithins53, I tested in version 6.0

Can you also test in on version 5.9 and report? I will also report after testing.

Again, I tested in version 5.9. Its works properly.

Yes, Works fine. Thank You.

[nithins53]

@SergeyBiryukov ON 6.1 beta 1 the font change is correctly reflected without the patch. But the issue still persists on 6.0.

UPDATE: The issue is still there. Tested it again

[sabernhardt]

Related: GB42246, possibly fixed by GB43195

The paragraph font size of 1.75em (or 1.25em when aligned left or right) is removed from the Pullquote block styles now.

I tried each font preset (Small, Medium, Large and Extra Large) plus some custom font sizes in WordPress 6.1 beta 2. The editor font size matched the front.

[audrasjb]

Since it appears it was fixed upstream on Gutenberg's side during the beta cycle, let's close this as reported-upstream. If the issue reappears after RC1 is released, please reopen the ticket :)