-
Notifications
You must be signed in to change notification settings - Fork 109
fix/guest user dialog #7555
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/guest user dialog #7555
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #7555 +/- ##
==========================================
+ Coverage 53.45% 60.12% +6.66%
==========================================
Files 502 502
Lines 43542 38566 -4976
Branches 1128 1128
==========================================
- Hits 23277 23186 -91
+ Misses 20157 15272 -4885
Partials 108 108 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
a5f1745 to
5959124
Compare
|
/backport to stable31 |
|
In
|
Yes... it's intentional. We show up to three users plus the people Icon. I see there's room for improvement 😉 - but I also have no simple idea of what else to do. |
Great catch! Turns out it was not used since it was introduce in drumroll 2019. |
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.
Nice improvements @max-nextcloud. Dropping a few design related comments:
- When the guest username is not defined, instead of the question mark I suggest we use a regular
usericon
-
In "Guest sees admin and form
now without duplicate entry for themselves"- I would not show an input field, instead I would show a list item with avatar, the string "you", and a right align secondary "edit" button with
pencilicon. Clicking that would activate the input. - The input field here should be horizontally aligned with the left icon and button, right now they're slightly misaligned
- I would not show an input field, instead I would show a list item with avatar, the string "you", and a right align secondary "edit" button with
-
In "Guest starts entering new name Now with NcInputField"
- Once in edit mode, the icon here could be hidden and the input field could expand to the left
- I think it would still be good to have a submit button in the same place as the edit one, otherwise it's a bit confusing. I'd make it also primary in this case and with the icon:
check.
2c5ff91 to
186a915
Compare
I think I addressed them all. Let me know if I misunderstood something or something else comes up Bildschirmaufzeichnung.vom.2025-08-24.12-30-33.mp4 |
d806f7e to
3fad811
Compare
|
Also not related to this PR but |
|
In |
Signed-off-by: Max <[email protected]>
Signed-off-by: Max <[email protected]>
Signed-off-by: Max <[email protected]>
Signed-off-by: Max <[email protected]>
Signed-off-by: Max <[email protected]>
Signed-off-by: Max <[email protected]>
Also remove `required: false` as that is the default. Signed-off-by: Max <[email protected]>
Use `var(--default-clickable-area)` in css instead. Signed-off-by: Max <[email protected]>
Signed-off-by: Max <[email protected]>
Signed-off-by: Max <[email protected]>
Signed-off-by: Max <[email protected]>
Signed-off-by: Max <[email protected]>
Signed-off-by: Max <[email protected]>
... and we never used it and mixed it with the session id. Signed-off-by: Max <[email protected]>
It is included in json serialize in `Db/Session.php` but not fetched for most cases in `Db/SessionMapper.php`. This results in empty values in the response so we better ignore them on the client side. Exposing them for other sessions than ones own would be security issue. Signed-off-by: Max <[email protected]>
UserSession has userId and displayName GuestSession has guestName (which may be an empty string). Signed-off-by: Max <[email protected]>
Signed-off-by: Max <[email protected]>
575b629 to
b116719
Compare
The conditional rendering somehow caused the icon to sometimes not be rendered leaving the button empty. This will need another rework anyway to integrate with the new guest user settings in @nextcloud/auth. Signed-off-by: Max <[email protected]>
We load the guestName from localStorage, send it to the server, and then store it again. That would make sense if the server changed it. But i do not see why it would do that if it did not do it the last time the name was changed and stored in localStorage. Signed-off-by: Max <[email protected]>
We used to set this on the guests side but then the translation is for the guests language. Better to set it on the current users side so it is translated according to the viewers language. Signed-off-by: Max <[email protected]>
It was only applied in the popup. Signed-off-by: Max <[email protected]>
b116719 to
4f691ed
Compare

Lots of fixes to the guest user dialog:
disabled(loading) andsuccessstate.<form>in<li>to use in<ul>)Screenshots
now with colors
now without duplicate entry for themselves
Now with NcInputField
with feedback now
now with updated name and color.
(used to use an outdated color and name)