passbolt / passbolt_api

Passbolt Community Edition (CE) API. The JSON API for the open source password manager for teams!
https://passbolt.com
GNU Affero General Public License v3.0
4.63k stars 306 forks source link

HostGator login site - password field has mixed behaviors #457

Closed garrettboone closed 1 year ago

garrettboone commented 1 year ago

HostGator login site - password field has mixed behaviors

What you did

  1. Navigate to https://portal.hostgator.com/login
  2. Email Address field shows in-form passbolt icon, and clicking the icon-then-resource populates the field correctly
  3. Click Next, which opens up the password field
  4. The password field is showing the in-form passbolt icon, but when clicking the icon-then-resource populates the field with a password that does not work (not sure what is pasted because it's hidden)
  5. If I open the extension and click Use on this page - it also does not work.
  6. However, if I copy the password and paste manually, it works.

What happened

At some point the following error was registered in the extension: image

There was also an extension message on one attempt to reproduce that said to paste and that the password could not be used on the page. I could not get the message to show again.

What you expected to happen

I guess if the icon shows, that it would work.

Also, I am noticing the icon does not show in the fields unless I hover over the fields - is that correct behavior?

cedricalfonsi commented 1 year ago

Hello @garrettboone,

Thank you for this Christmas bug report 🎄 Internal ticket reference: PB-21900

garrettboone commented 1 year ago

🎁Merry Christmas!

Benj1er commented 1 year ago

Hello @garrettboone,

This error mentioned can happen in some cases. When the browser goes to another url, the application listens to an event to check if the port is still connected. Unfortunately in some cases the port will be disconnected by the browser long after this event which leads to this error. For the moment, to fix this, a refresh of the page is necessary.

This is a known problem on our side and with the transition from MV2 to MV3, the browser events will be better managed and this type of error will be fixed.

Benj1er commented 1 year ago

Fixed with v4.1.2, don't hesitate to reopen it if the issue persists.