Make WordPress Core

Opened 3 years ago

Last modified 3 years ago

#52794 new defect (bug)

Blocks not entering in correct place

Reported by: amyolsen12's profile amyolsen12 Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 5.7
Component: Editor Keywords: reporter-feedback
Focuses: Cc:


I updated to WordPress 5.7, and ever since it's had this new glitch. Especially when I open a post and go to add a block for the first time in that session, it will insert the block at the very end of the post, instead of in the middle where I wanted it. Usually after that first glitch it works fine, but every once in a while it will do it again though I haven't determine the pattern for that one.

Also, if I ever click out to the side of a block, perhaps to get a clearer image of what I just did, it will scroll me all the way down to the bottom of the post. This happens every time I do that. Since I use a lot of images, this is a huge annoyance.


Change History (5)

#1 @desrosj
3 years ago

  • Component changed from General to Editor
  • Keywords reporter-feedback added
  • Milestone changed from Awaiting Review to 5.7.1

Hi @amyolsen12!

Thanks for this report.

For the first item, can you clarify whether you had placed your cursor in the editor where you wanted the block to be inserted before? Or were your steps to open the post, click the block inserter in the top toolbar, and click the block you would like?

Would it be possible to get a screen recording of both items happening?

Moving to the 5.7.1 milestone to investigate.

#2 @talldanwp
3 years ago

@amyolsen12 Just following up on this, have you had a chance to figure out how make this happen?

As @desrosj mentions, this does seem to happen if the + button at the top is clicked before any blocks in the post are selected, but I think this is how it has always worked.

This ticket was mentioned in Slack in #core by audrasjb. View the logs.

3 years ago

This ticket was mentioned in Slack in #core by audrasjb. View the logs.

3 years ago

#5 @audrasjb
3 years ago

  • Milestone changed from 5.7.1 to Awaiting Review


Moving this ticket back to the Awaiting review list, until we can get steps to reproduce the issue.


Note: See TracTickets for help on using tickets.