#58847 closed defect (bug) (fixed)
Block editor layout issue
Reported by: | bhrugesh12 | Owned by: | audrasjb |
---|---|---|---|
Milestone: | 6.3 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Editor | Keywords: | has-patch commit reporter-feedback fixed-major |
Focuses: | ui, css | Cc: |
Description
In WP RC1
When i try to edit any post and page, then trying to add block via add icon in editor. It seems to be so far as per previous version compare.
Attachments (5)
Change History (22)
#1
in reply to:
↑ description
@
14 months ago
#4
follow-up:
↓ 6
@
14 months ago
- Milestone changed from Awaiting Review to 6.3
I can't reproduce the issue using TT3 theme.
(Chrome / Mac OS / 13")
Let's still milestone this to 6.3.
#5
@
14 months ago
This issue was thought to be fixed in https://github.com/WordPress/gutenberg/pull/52356 which was included in 6.3 Beta 4.
I can reproduce it on 6.3 RC1, as well as on the 6.3 release branch, though I can't on trunk. Not 100% sure what's happening here, will continue investigating.
#6
in reply to:
↑ 4
@
14 months ago
Replying to audrasjb:
I can't reproduce the issue using TT3 theme.
(Chrome / Mac OS / 13")
Let's still milestone this to 6.3.
Please check attached video for better understanding.
This ticket was mentioned in PR #4871 on WordPress/wordpress-develop by @isabel_brison.
14 months ago
#7
- Keywords has-patch added
To avoid breaking updates.
Trac ticket: https://core.trac.wordpress.org/ticket/58847
Essentially copies the fix from the previous time we had this problem: https://github.com/WordPress/wordpress-develop/pull/4155#discussion_r1121383013
Hope we can make our popovers work with the latest versions of those packages before too much longer 😅 but given it's RC time again this seems like the safest option for now.
@huzaifaalmesbah commented on PR #4871:
14 months ago
#8
Thank you very much for this solution. @tellthemachines
#9
@
14 months ago
Thanks @isabel_brison for the PR, Is it part of GB backport or we merge it right away?
#10
@
14 months ago
- Keywords commit reporter-feedback added
I can reproduce it on 6.3 RC1, as well as on the 6.3 release branch, though I can't on trunk.
Mmmm, weird. Could it be some sort of "caching gremlins" (may even be npm caching the packages)? :)
Cannot reproduce it. Tested both trunk and the 6.3 branch, in Firefox and Chromium, specifically tested in /build (same as production) with SCRIPT_DEBUG disabled.
The patch seems simple enough, and safe enough so thinking it can be committed to trunk if that will facilitate testing (the latest nightly build is here: https://wordpress.org/nightly-builds/wordpress-latest.zip). Then anybody that is experiencing this can test trunk and see if it fixes it, and if yes we can backport it to the 6.3 branch.
#12
@
14 months ago
Thanks @azaozz! I've committed the patch to trunk.
I was able to reproduce the issue eventually on trunk by deleting the node_modules and reinstalling. For folks testing the fix, try doing this on both trunk and the 6.3 branch and check the popover positioning each time.
@isabel_brison commented on PR #4871:
14 months ago
#13
Committed to trunk in r56284. Pending testing on trunk to check the issue is fixed, we can then commit it to the release branch.
#14
@
14 months ago
- Keywords fixed-major added
- Owner set to audrasjb
- Status changed from new to reviewing
Adding fixed-major
workflow keyword.
Self assigning for review and potential backport to branch 6.3.
This ticket was mentioned in Slack in #core by audrasjb. View the logs.
14 months ago
@audrasjb commented on PR #4871:
14 months ago
#17
committed in https://core.trac.wordpress.org/changeset/56289
Replying to bhrugesh12: