Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Learn More

LastPass virtual keyboard not coming up when trying to login via LastPass icon after Firefox 57.0.

  • Brez odgovorov
  • 1 ima to težavo
  • 8 ogledov
more options

After Firefox updated to 57.0 (Quantum) this morning, my LastPass add-on/extension would not properly display the virtual keyboard for signing in. I had to go to lastpass.com and use the sign-in there to get the virtual keyboard functionality to work. The add-on is 4.2.1.21a. Is there a setting I need to update to get this to work again, or did LastPass lose the functionality under Firefox 57.0?

At present, when I click on the virtual keyboard icon when using the LastPass icon for signing on, the screen changes as usual and leaves the sign-on window in the middle of the screen and does not bring up the virtual keyboard to the left of it (after moving the sign-on pop-up to the right a bit).

One potential solution, update of the Lastpass addon, was supplied by Pkshadow, but it did not resolve the issue, as the update was already in place.

After Firefox updated to 57.0 (Quantum) this morning, my LastPass add-on/extension would not properly display the virtual keyboard for signing in. I had to go to lastpass.com and use the sign-in there to get the virtual keyboard functionality to work. The add-on is 4.2.1.21a. Is there a setting I need to update to get this to work again, or did LastPass lose the functionality under Firefox 57.0? At present, when I click on the virtual keyboard icon when using the LastPass icon for signing on, the screen changes as usual and leaves the sign-on window in the middle of the screen and does not bring up the virtual keyboard to the left of it (after moving the sign-on pop-up to the right a bit). One potential solution, update of the Lastpass addon, was supplied by Pkshadow, but it did not resolve the issue, as the update was already in place.