-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
enh(UnifiedSearch): Keep the searchbar on top of the modal #42184
Conversation
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.
Why is there a lot of whites pace changes? When this already passes out lint check? Unless the white space changes are necessitated by the changes required for this work, I think it's better we have commit that does exactly what the commit says and another one for the white space changes.
It might be worthwhile to introduce and editor-config file to make everyone always ends up with the same set of white space changes.
The sticky search bar look better though....🚀🚀
@fenn-cs because I needed to indent the search bar one level meaning there is a wrapper div to keep all sticky parts in place (see the "...__header" class). |
b78a856
to
7225981
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Signed-off-by: Ferdinand Thiessen <[email protected]>
7225981
to
ac2182c
Compare
This comment was marked as resolved.
This comment was marked as resolved.
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.
@susnux now there’s no whitespace on the right of the hover/focus box – it should have the same amount on the right as it has on the left:
Sorry for all the little feedback – is this actually an issue with the component that other modals would have to fix on their own also? These are things which need to work out of the box, so might be better to fix in the component directly?
@jancborchardt this is not related and an issue with the vue library - it will be fixed with the next release - ref: nextcloud-libraries/nextcloud-vue#4956 With that it will look like this: vokoscreenNG-2023-12-18_15-28-55.mp4 |
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.
Thanks for the info @susnux – looks great now. :)
/backport to stable28 |
The backport to stable28 failed. Please do this backport manually. # Switch to the target branch and update it
git checkout stable28
git pull origin stable28
# Create the new backport branch
git checkout -b fix/foo-stable28
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable28 Error: Unknown error More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport |
/skjnldsv-backport to stable28 |
Summary
For me it is a bit inconvenient that I have to scroll all the way up to change the search query if I was scrolling through the results of the new unified search modal.
Therefor I changed the modal to keep the search bar and filter on top while scrolling (except for very small screens where this would be an accessibility problem).
Note The diff looks worse than it is due to white space changes...
Screencast
After ✨
vokoscreenNG-2023-12-13_01-13-02.mp4
Before
vokoscreenNG-2023-12-13_01-13-35.mp4
Checklist