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

[Data Object] Many To Many Relation field list reorder freeze #5683

Closed
logical-luke opened this issue Jan 28, 2020 · 2 comments · Fixed by #5848
Closed

[Data Object] Many To Many Relation field list reorder freeze #5683

logical-luke opened this issue Jan 28, 2020 · 2 comments · Fixed by #5848
Assignees
Labels

Comments

@logical-luke
Copy link

Bug Report

Expected behavior

Elements on the list are have changed order and browser is responsible.

Actual behavior

Browser is freezing during moving

Steps to reproduce

  1. Create object with Many to Many Relation field
  2. Add at least 25 relation elements
  3. Move quickly elements from bottom to top and in reverse way

Browser should freeze after few movements. We can wait until timeout error message will occur and decide if we want to terminate card or not. During one of tries I was able to catch JS console error
DevTools - zeus-ng-frontend-int joyn de-admin-?_dc=1579873488 perspective=_101

Reproduced on

Pimcore 6.4.0
Google Chrome Version 79.0.3945.130 (Official Build) (64-bit)

@NiklasBr
Copy link
Contributor

NiklasBr commented Feb 2, 2020

Looks very similar to #3009 and #3559.

@brusch brusch added the Bug label Feb 7, 2020
@brusch brusch changed the title Many To Many Relation field list reorder freeze [Data Object] Many To Many Relation field list reorder freeze Feb 7, 2020
@dvesh3 dvesh3 self-assigned this Feb 17, 2020
@dvesh3
Copy link
Contributor

dvesh3 commented Feb 17, 2020

@weisswurstkanone extjs issue, fixed already for advanced types ebca1cb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants