We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Autocomplete disabled at Chase.com

  • 3 Mbohovái
  • 2 oguereko ko apañuãi
  • Mbohovái ipaháva cor-el

more options

Recently, Chase seems to have disabled autocomplete on their login pages (www.chase.com and secure.chase.com). Saved usernames and passwords no longer auto-populate. Yet, Chrome and Edge have been unaffected. Can anyone at Mozilla address this?

Recently, Chase seems to have disabled autocomplete on their login pages (www.chase.com and secure.chase.com). Saved usernames and passwords no longer auto-populate. Yet, Chrome and Edge have been unaffected. Can anyone at Mozilla address this?

Opaite Mbohovái (3)

more options

Hi I'm not sure what goes wrong here. I'm not seeing "Use Saved Password" if I right-click the username field, so Firefox doesn't recognize those fields as belonging to a login form. This could be caused by a hidden input field further down in the DOM (the Inspector isn't working properly on the Chase website for some reason for me).

Maybe file a bug report to let the Firefox developers look into this and possibly create a recipe.

¿Imba’eporãva?

more options

When I inspect the field, I see that Chase has set autocomplete to "off." But that doesn't explain why it's only affecting Firefox users. I'll file the bug report as suggested.

¿Imba’eporãva?

more options

autocomplete="off" shouldn't have effect as this is normally ignored, only usual values for autocomplete have been reported in the past to cause issues.

¿Imba’eporãva?

Eporandumína

Nde eikéke nde mba’etepe embohovái hag̃ua ñe’ẽmondo. Ikatúpa, emoñepyrũ peteĩ porandu, ndereguerekói gueteriramo nemba’ete.