Avatar for Username

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Learn More

Esta discussão foi arquivada. Se precisar de ajuda, por favor, coloque uma nova questão.

Why is it, that FF deactivate Kaspersky Virtual Keyboard for secure input, in any version of FireFox for OS X other than 48.0.2, yet the add-on is still operati

  • Nenhuma resposta
  • 1 tem este problema
  • 1 visualização
ChillensSpace
ChillensSpace
more options

IF, and only if I upgrade to 48.0.2, do what appears to be a mozilla page, do I get indications that the Kaspersky (secure input) virtual keyboard may work and isn't disabled, but the exact same add-on, has been ruled, accordingly to what appears to be a mozilla source, disabled and any previous version that I am/was running? Where is the option(s) for the individual to over ride such unilateral actions, and affords the individual(s) to take responsibility(ties) for running a add-on that IS verified on this latest version, that appears to have came out today? 

    How can I over ride this, and self authorize the Virtual Keyboard add-on to run in a previous version?
IF, and only if I upgrade to 48.0.2, do what appears to be a mozilla page, do I get indications that the Kaspersky (secure input) virtual keyboard may work and isn't disabled, but the exact same add-on, has been ruled, accordingly to what appears to be a mozilla source, disabled and any previous version that I am/was running? Where is the option(s) for the individual to over ride such unilateral actions, and affords the individual(s) to take responsibility(ties) for running a add-on that IS verified on this latest version, that appears to have came out today? How can I over ride this, and self authorize the Virtual Keyboard add-on to run in a previous version?