Sending Wrong Credentials for Schedules Direct

[crackulator]

Version: 5.0.0.191007 on Ubuntu, Firefox
Can't get it to bring in my channel list from Schedules Direct.
If you look at this log, you can see two of the three times it hit SD it used "username: xbmc", which is my NextPVR login, not my SD login. I can guarantee you I put in my SD credentials every time I attempted it, but for some reason it's sending the wrong credentials.

I would suspect it has something to do with autofill. Every time I arrive at an SD login, it has filled it with my NextPVR credentials. I change it before continuing, but somehow it's not registering.

Maybe the field names for the logins are the same, so autofill thinks they're the same fields, and they should be different?

[mvallevand]

I disabled autofill on the NextPVR server IP's a long time ago because I was having too many issues that I could not resolve.

Martin

[sub]

Maybe the field names for the logins are the same, so autofill thinks they're the same fields, and they should be different?

It's annoying how some browsers behave around this stuff. These fields have actually got different names ("schedulesDirectUsername" and "schedulesDirectPassword", where as the login screen is called "username" and "password"). I think firefox just sees it's a password field (ie because we want hidden text), so decides to force it's password in there anyway.

I've had a go at a slight change for the next release which will hopefully help.

[crackulator]

Maybe the ID attribute?
"Firefox also appears to look at the id in addition to the name attribute"
https://cloudfour.com/thinks/autofill-wh...-but-dont/

[sub]

Actually, when I said "name" above, I meant "id". I don't set a name attribute on any fields.

<input type="text" id="schedulesDirectUsername" placeholder="SD Username">

[mvallevand]

Wouldn't it be better to turn autocomplete off for both the SD fields since you populate them via the API rather then doing it via the browser?

Edit I see you do but you also have an id so not sure where this will change?

Martin

[sub]

Wouldn't it be better to turn autocomplete off for both the SD fields since you populate them via the API rather then doing it via the browser?

It is off for the next build.

[mvallevand]

I re-enabled auto complete I played around with the SD HTML and ended up with that stupid "nosusername" [[[~ second saved password with lots of prompts during navigation which was my initial problem with autocomplete. Maybe you also have to do something else with the pin?

Martin