-
-
Notifications
You must be signed in to change notification settings - Fork 62
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 Photos not shown in large browser windows #630 #664
Conversation
Sorry, I don't know how to fix the last missing check, but the code changes are minimal, so you could probably merge it without those changes.... |
/compile / |
src/services/GridConfig.js
Outdated
@@ -44,7 +44,7 @@ export default new Vue({ | |||
methods: { | |||
handleWindowResize() { | |||
// find the first grid size that fit the current window width | |||
const currentSize = Object.keys(sizes).find(size => size > document.documentElement.clientWidth) | |||
const currentSize = Object.keys(sizes).find(size => size > document.documentElement.clientWidth || size === 'max') | |||
this.gridConfig = sizes[currentSize] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer the fallback on the this.gridConfig assignment instead.
this.gridConfig = sizes[currentSize] | |
// fallback to max if none matches | |
this.gridConfig = sizes[currentSize] || sizes['max'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be more elegant, sorry I am not a javascript guy 😊😊
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries :)
Can you do the change so I can approve? :)
OK, still fighting with the automatic checks. Thanks for teaching the power of || in javascript, Detlef |
This comment has been minimized.
This comment has been minimized.
/backport to stable21 |
/backport to stable20 |
/backport to stable19 |
Thanks @dsmic Because I can't rebase now, please either enable write permissions or rebase yourself this branch to master 😉 |
Ah, my bad, it seems we have the permissions, no idea why my push failed. |
Yeah, I can't rebase and push, @dsmic please rebase, and drop changes on /js so we can update the bundles again :) |
Sorry, but I don't know, why it closed the pull request. I cleaned my fork ... |
This comment has been minimized.
This comment has been minimized.
Ah, you didn't rebased to latest master! |
Signed-off-by: detlef <ds2@physik.de>
Signed-off-by: npmbuildbot-nextcloud[bot] <npmbuildbot-nextcloud[bot]@users.noreply.github.com>
Am I supposed to commit my changes from the build? 'Zum Commit vorgemerkte Änderungen: Unversionierte Dateien: |
Yes, this repo expect npm bundles to be up--to-date before merging |
This comment has been minimized.
This comment has been minimized.
Signed-off-by: detlef <ds2@physik.de>
I still get node12.x failing: `Uncommited changes in webpack build no changes added to commit (use "git add" and/or "git commit -a") |
As the title says: this should fix this issue, as the max: key was not handled properly before
Fix #630