-
-
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
[Bug]: Autofill “Share label” and “Set password” fields when editing a shared link #44451
Comments
Hello, I upgraded yesterday from 26.0.12 to 27.1.7 and have since witnessed the exact same problem. |
Same here. Annoying bug. Too much JavaScript... Please keep it simple. |
What you see there is not Nextcloud filling out the fields but your browser from the saved passwords, not much we can do there. |
I will, of course, turn off autofill. But there are many users, such as accountants, managers. What should we do with them? |
Is it possible to name the input fields differently, without using the words “label” and “password”, so that the browser does not use autofill? |
I pushed a fixed waiting for reviews in #44575 :) |
Bug description
In nextcloud version 28.0.3, I discovered an unpleasant feature when editing custom permissions for a shared link.
The “Link name” and “Set password” fields are filled in automatically and are taken from the nextcloud user name and password saved by the browser.
Steps to reproduce
Expected behavior
The “Link name” and “Set password” fields must be empty
Installation method
Community Docker image
Nextcloud Server version
28
Operating system
Debian/Ubuntu
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: