Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Editor: When a mouse cursor is over "Add block" line, scrolling stops working #67182

Closed
3 of 6 tasks
goodpenguins opened this issue Nov 21, 2024 · 3 comments
Closed
3 of 6 tasks
Labels
[Type] Bug An existing feature does not function as intended

Comments

@goodpenguins
Copy link

Description

When scrolling content in the editor with mouse wheel, when the mouse cursor is over the "Add Block" line, even if it has not yet appeared, scrolling stops. Any direction.

Step-by-step reproduction instructions

Create a page/post with content 2-3 screens high. Start scrolling up and down the page. You will probably catch it. Or just place your mouse pointer between the blocks where the "Add Block" line should be and try scrolling.

Screenshots, screen recording, code snippet

Image

Environment info

WP 6.7
Gutenberg 19.7.0
Theme: Twenty Twenty-Five
OS: Windows 11
Browser: MS Edge

Please confirm that you have searched existing issues in the repo.

  • Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

  • Yes

Please confirm which theme type you used for testing.

  • Block
  • Classic
  • Hybrid (e.g. classic with theme.json)
  • Not sure
@goodpenguins goodpenguins added the [Type] Bug An existing feature does not function as intended label Nov 21, 2024
@im3dabasia
Copy link
Contributor

Hey @goodpenguins, I was able to reproduce this issue. Good find! This is happening because of the following CSS:

.components-popover.block-editor-block-popover__inbetween .is-with-inserter, .components-popover.block-editor-block-popover__inbetween .is-with-inserter *{
    pointer-events: all
}

@beixco
Copy link

beixco commented Nov 21, 2024

Hey, I have the same issue, and it's really annoying. Hope it can get fixed soon!

@talldan
Copy link
Contributor

talldan commented Nov 21, 2024

I believe this is already reported in #63260, so I'll close this as a duplicate.

There was some work in progress to fix the problem, which it'd be good to revisit and make sure it gets into a release.

@talldan talldan closed this as not planned Won't fix, can't repro, duplicate, stale Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Bug An existing feature does not function as intended
Projects
None yet
Development

No branches or pull requests

4 participants