[GH-ISSUE #592] Allow stored logins for browsers #422

Closed
opened 2026-02-26 02:33:09 +03:00 by kerem · 2 comments
Owner

Originally created by @ElectronicWar on GitHub (May 12, 2017).
Original GitHub issue: https://github.com/koel/koel/issues/592

Koel v3.6.2 on Debian Stretch, Node 6.10.3, yarn v0.23.4, PHP 7.0.16, MariaDB 10.1, Nginx 1.10.3 over HTTP/2

Currently, it's absolutely impossible to store or re-use any kind of login information in the login mask of Koel. You cannot double-click the username field for previously used logins nor does my browser offer to store the login.

Unfortunately I have no idea on how to fix that myself with a PR since it looks like a regular HTML form to me.

Originally created by @ElectronicWar on GitHub (May 12, 2017). Original GitHub issue: https://github.com/koel/koel/issues/592 Koel v3.6.2 on Debian Stretch, Node 6.10.3, yarn v0.23.4, PHP 7.0.16, MariaDB 10.1, Nginx 1.10.3 over HTTP/2 Currently, it's absolutely impossible to store or re-use any kind of login information in the login mask of Koel. You cannot double-click the username field for previously used logins nor does my browser offer to store the login. Unfortunately I have no idea on how to fix that myself with a PR since it looks like a regular HTML form to me.
kerem closed this issue 2026-02-26 02:33:10 +03:00
Author
Owner

@phanan commented on GitHub (May 12, 2017):

It's a normal ajax-based login form, and my Chrome offers saving credentials just fine. You should check your browser instead.

<!-- gh-comment-id:301113667 --> @phanan commented on GitHub (May 12, 2017): It's a normal ajax-based login form, and my Chrome offers saving credentials just fine. You should check your browser instead.
Author
Owner

@ElectronicWar commented on GitHub (May 15, 2017):

Little update: Problem only occurs with current Chrome stable. Looks like this is a Chrome-specific error and not directly related to Koel.

Does NOT work:

  • Chrome Stable v58

Does work:

  • Chrome Beta v59
  • Chrome Canary v60
  • Firefox v53
  • Edge v40

I am gonna wait for Chrome v59 to roll around, consider this case closed. Sorry for the troubles.

<!-- gh-comment-id:301415325 --> @ElectronicWar commented on GitHub (May 15, 2017): Little update: Problem only occurs with current Chrome stable. Looks like this is a Chrome-specific error and not directly related to Koel. Does NOT work: - Chrome Stable v58 Does work: - Chrome Beta v59 - Chrome Canary v60 - Firefox v53 - Edge v40 I am gonna wait for Chrome v59 to roll around, consider this case closed. Sorry for the troubles.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/koel-koel#422
No description provided.