Bug 280063 – Regression (Safari 18.0): WordPress Classic Editor sidebar layout is broken (floats not clearing)

• Status: RESOLVED
• Resolution: FIXED
• Component: Layout and Rendering

[zalan]

Demo link to run WP classic editor in your browser: https://playground.wordpress.net/?plugin=classic-editor&blueprint-url=https://wordpress.org/plugins/wp-json/plugins/v1/plugin/classic-editor/blueprint.json?rev=3122271

Reproduction steps:
1. Click Screen Options
2. Enable Custom Fields and Discussion

In Safari 18 the new meta boxes are overlapping content on the right of the screen. In Safari 17 and other browsers they show below the post content as expected.

<rdar://136362683>

[zalan]

Created attachment 472615 [details]
Test reduction

This is about negative horizontal margin on floats.

[zalan]

Created attachment 472675 [details]
Patch

[zalan]

Created attachment 472678 [details]
[fast-cq]Patch

[EWS]

Committed 284247@main (dffa25228983): <https://commits.webkit.org/284247@main>

All reviewed patches have been landed. Closing bug and clearing flags on attachment 472678 [details].

[zalan]

Created attachment 472680 [details]
Screenshot with the fix applied

[EWS]

Committed 283286.156@safari-7620-branch (6aeec1ea5a94): <https://commits.webkit.org/283286.156@safari-7620-branch>

Reviewed commits have been landed. Closing PR #1938 and removing active labels.

[Eduard Comănici]

Do you guys mind me asking when this will ship?

I rely on Safari and WordPress for my job and it is really annoying to use the "1 column" trick or other hacks. :(

[peterwilsoncc]

An update of the classic editor has been shipped with a workaround, therefore the reproduction URL above will no longer show the regression.

You can use this updated link to test on WordPress playground with a version of the classic editor without the fix:

https://playground.wordpress.net/?plugin=https%3A%2F%2Fdownloads.wordpress.org%2Fplugin%2Fclassic-editor.1.6.3.zip&url=%2Fwp-admin%2Fpost-new.php

The rest of the reproduction steps remain the same.

[Eduard Comănici]

Peter,

I see. However, my workflow does not involve the Classic Editor directly, but WooCommerce. Woo still uses a variant of the classic editor, not the plugin directly. :)

[zalan]

*** Bug 281744 has been marked as a duplicate of this bug. ***