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

Block dragging does not trigger automatic page scrolling #6321

Closed
MrKarlDilkington opened this issue Jan 21, 2018 · 5 comments · Fixed by #6334
Closed

Block dragging does not trigger automatic page scrolling #6321

MrKarlDilkington opened this issue Jan 21, 2018 · 5 comments · Fixed by #6334
Assignees
Labels
Type:Bug Existing functionality not performing as expected.

Comments

@MrKarlDilkington
Copy link
Contributor

MrKarlDilkington commented Jan 21, 2018

When dragging blocks up and down a page, the page is not scrolling automatically. This problem was reported in a closed issue, so I created a new issue to make sure it doesn't get lost.
#36 (comment)

This issue affects concrete5 5.7 and 8.

Block drag scrolling is broken in:

  • Chrome
  • Firefox
  • Opera

Block drag scrolling is working correctly in:

  • Internet Explorer 11
  • Edge 16
@aembler
Copy link
Member

aembler commented Jan 22, 2018

Strangely, Safari appears to work just fine as well.

@aembler aembler added Type:Bug Existing functionality not performing as expected. priority:love to have labels Jan 22, 2018
@mnakalay
Copy link
Contributor

I can confirm it doesn't work in Chrome and Firefox

@MrKarlDilkington
Copy link
Contributor Author

@aembler

This issue appears to affect any moving in edit mode, including moving blocks and layouts. Scrolling the page now requires using the scroll wheel, up/down arrow keys, or page up/page down keys while dragging.

Based on the browsers affected (Chrome is the most popular browser) and how much it affects the editing experience, can we relabel this to "priority:must have", please?

@dominikkremer
Copy link

Hey folks,

first time contributing to concrete5.

I looked into it today and did some debugging but couldn‘t find the cause of the problem.

Every hint or piece of information regarding this issue appreciated.

Will further look into it.
Thanks!

@mlocati
Copy link
Contributor

mlocati commented Jan 24, 2018

#6334 should fix this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type:Bug Existing functionality not performing as expected.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants