You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created a little user script to add an ID "login" as a workaround. Now the login field is correctly recognized and can be filled with credentials again:
Userscript (not working anymore)
// ==UserScript==// @name Steam: Add login input field id// @namespace Violentmonkey Scripts// @match https://store.steampowered.com/login/// @match https://steamcommunity.com/login/home/// @grant none// @version 1.0// ==/UserScript==// https://stackoverflow.com/a/61511955functionwaitForElement(selector){returnnewPromise(resolve=>{if(document.querySelector(selector)){returnresolve(document.querySelector(selector));}constobserver=newMutationObserver(mutations=>{if(document.querySelector(selector)){resolve(document.querySelector(selector));observer.disconnect();}});observer.observe(document.body,{childList: true,subtree: true});});}// Assume first match is the user id login inputwaitForElement("input[class^='newlogindialog_TextInput']").then((element)=>{element.setAttribute('id','login');});
Image
Feel free to close :)
The text was updated successfully, but these errors were encountered:
It's a shame that the Steam login form does not use proper <label> elements or name and id attributes. Without those, I don't think there is anything we can do about this on our side.
Thanks for the ping, I actually forgot about this and was just recently annoyed of this (again!) because the workaround above isn't actually working anymore. The classes are now all random chars.
Updated workaround:
Userscript
// ==UserScript==// @name Steam: Add login input field id// @namespace Violentmonkey Scripts// @match https://store.steampowered.com/login/// @match https://steamcommunity.com/login/home/// @grant none// @version 1.0// ==/UserScript==// https://stackoverflow.com/a/61511955functionwaitForElement(selector){returnnewPromise(resolve=>{if(document.querySelector(selector)){returnresolve(document.querySelector(selector));}constobserver=newMutationObserver(mutations=>{if(document.querySelector(selector)){resolve(document.querySelector(selector));observer.disconnect();}});observer.observe(document.body,{childList: true,subtree: true});});}// Wait for login form// Assume first match is the user id login inputwaitForElement('div[data-featuretarget="login"] input[type="text"]').then((element)=>{element.setAttribute('id','login');});
This isn't an issue but a workaround.
Since the sign-in rework some time ago the user id input fields weren't recognized anymore at:
Image
After some digging I figured that's because there's no identification in the HTML:
HTML
I created a little user script to add an ID "login" as a workaround. Now the login field is correctly recognized and can be filled with credentials again:
Userscript (not working anymore)
Image
Feel free to close :)
The text was updated successfully, but these errors were encountered: