Open Bug 1119083 Opened 6 years ago Updated 1 year ago

Breakdown: Support capturing and filling of login credentials on hulu.com

Categories

(Toolkit :: Password Manager, defect, P2)

defect

Tracking

()

People

(Reporter: ckarlof, Unassigned)

References

(Depends on 1 open bug)

Details

(Whiteboard: [platform-rel-Hulu])

Attachments

(1 file)

Attached image hulu.gif
hulu.com is a password manager gauntlet. In my experience, working on hulu.com means you work in lots of other places. When I hear about a new browser based password manager, the first site I test it on is hulu.com. :)

Some challenges on Hulu:

* it doesn't use a <form> element on http://www.hulu.com
* the login "form" is dynamically added after page load (i.e., no input type=password on page load)
* the password input is initially hidden and only becomes visible after the user focuses on the username or password field
* credential submission uses AJAX and does not navigate the page to a new URL
* the login form is on an HTTP page
* they have a totally different login experience on https://secure.hulu.com/account/signin, which *does* use a <form> element 

This makes capturing difficult because you can't rely on onsubmit or page navigation as a cue to ask the user if they want to save their credentials. It makes auto-fill challenging because the password field is not initially visible. The fact the whole thing is on an HTTP page raises security concerns.

Screencap attached.
Whiteboard: [platform-rel-Hulu]
Priority: -- → P2
You need to log in before you can comment on or make changes to this bug.