#1131 Autotype speed is influenced by Javascript (KP v2.22)

KeePass_2.x
closed
nobody
5
2013-07-07
2013-07-03
Alpengreis
No

Hi,

Autotype speed is influenced by Javascript:

To reproduce it with Firefox:

1a) Start KeePass
1b) Start Notepad
2 ) Test the speed of Autotype in Notepad window
3a) Start Firefox and surf to http://www.teleboy.ch
3b) Make sure, that Javascript is allowed (for this domain)
3c) If you use NoScript (or something similar), make sure, that @font-face is not forbidden.)
3c) Click "Login" on the website
4 ) Retest the speed of Autotype in Notepad window

Explanation:

After the click on "Login", the speed of Autotype is much faster until Firefox (resp at least the Tab/Window) is closed. If Javascript is disabled (or at least @font-face is forbidden), speed is unaffected.

Fix:

The (defined) speed of Autotype should remain, regardless of whether JS is in use or not!

Best regards,

Norbert Schneider
Aka SwissBit

Discussion

  • Dominik Reichl
    Dominik Reichl
    2013-07-06

    • status: open --> closed
     
  • Dominik Reichl
    Dominik Reichl
    2013-07-06

    I followed your steps exactly, but cannot reproduce the issue. The auto-type speed remains the same. I also cannot imagine how a browser would influence auto-type into another window; KeePass is completely independent of browsers.

    Maybe you're using a plugin, browser extension or security software that interfers with auto-type.

    Best regards,
    Dominik

     
  • Alpengreis
    Alpengreis
    2013-07-07

    Hi Dominik, thanks for answering!

    Just for information: the browser does not have DIRECT influence on another window, but he changed "only" the speed of autotype (in memory?). After closing the browser, the speed of autotype is resetted and working normally again. This behavior can be accomplished by the way also with Google Chrome and has (at least with Fx, because tested) nothing to do with plug-ins.

    Maybe a driver (keyboard) play a role? Or just the resident AV scanner (F-Secure).

    I'll stay tuned ... maybe I'll find out the reason yet.


    In Deutsch (German), zur besseren Erklärung meinerseits (hoffentlich g):

    Nur noch zur Information: der Browser hat nicht DIREKTEN Einfluss auf ein anderes Fenster, sondern er verändert "nur" die Geschwindigkeit von AutoType (im Speicher?). Nach Schliessen des Browsers, wird die Geschwindigkeit zurückgesetzt und AutoType arbeitet wieder normal. Das Verhalten lässt sich übrigens auch mit Google Chrome bewerkstelligen und hat (zumindest mit Fx, weil getestet) nichts mit PlugIns zu tun.

    Vielleicht spielt auch ein Treiber (Tastatur) eine Rolle? Oder eben der residente AV-Scanner (F-Secure).

    Ich bleibe dran, vielleicht finde ich den Grund ja noch raus.


    Anyway, best wishes,
    SwissBit