With sessions, you're logged in for as long as your browser keeps the cookie. So something at your end is nuking the cookie. Private browsing? An extension?
With password managers, it's fairly standard that they nuke the value of the field before inserting the password, but even then it's illustrative as most password managers have an idea of the page as it's displayed, and the hidden fields on the page. Password managers will populate the hidden fields as well as the visible fields, meaning that when you hit submit the password is likely put into the hidden field and what you typed in was ignored (unless you were explicitly overriding the password manager by changing the values of most fields).
Not sure where the bug is there.
With sessions, you're logged in for as long as your browser keeps the cookie. So something at your end is nuking the cookie. Private browsing? An extension?
With password managers, it's fairly standard that they nuke the value of the field before inserting the password, but even then it's illustrative as most password managers have an idea of the page as it's displayed, and the hidden fields on the page. Password managers will populate the hidden fields as well as the visible fields, meaning that when you hit submit the password is likely put into the hidden field and what you typed in was ignored (unless you were explicitly overriding the password manager by changing the values of most fields).
Doesn't sound like either thing is a bug.