-
Notifications
You must be signed in to change notification settings - Fork 102
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
Fix: Filter for relation throws an error #741
Conversation
@kingjia90 What did you config as width? |
@kingjia90 I changed it again 1bddd12 |
@kingjia90 What did you set as the width? I entered 1000 in this field in the demo, and it is now wider. Yes, the columns are narrow, but I believe that’s because they are empty at the beginning. |
@kingjia90 I cleared the browser cache/cookies. Now the column widths also correct. Extjs saves the widths of the columns in the local storage: |
Quality Gate passedIssues Measures |
i didn't set anything, that should be right, nevermind, it is just fine
ahhh didn't know that... does it implicitly mean that we cannot use variable width and should be always fixed? |
@kingjia90 It's not from ext js. It is here in the admin-ui-classic-bundle: admin-ui-classic-bundle/public/js/pimcore/object/tags/manyToManyObjectRelation.js Lines 405 to 426 in e3b66fb
admin-ui-classic-bundle/public/js/pimcore/object/tags/abstractRelations.js Lines 210 to 225 in e3b66fb
You have first open the filter with the very small window. So the columns was saved small. You can drag and drop the widths wider and it should be saved for the next window, right? When you have a empty local storage the columns have a correct width. |
It seems it's because the grid is likely empty on first time opening as "Filter by relation" and therefore it doesn't have an estimation on how long each column would be. Ideally we should trigger this resize with The current PR changes LGTM |
Fix: #720