RoboForm & Chrome

Unofficial forums for RoboForm and Google Chrome.

Register or log in - lost password?

RoboForm: Learn more...
RoboForm & Chrome » RoboForm Forum

Google Chrome Tab Change Fails When Roboform Toolbar Extension is enabled

(1 post) (1 voice)
  • Started 2 years ago by Locadony5b

Tags:

  • abercrombie fr
  • abercrombie pas cher
  • Air Jordan 3s
  • air max 87
  • cheap snapbacks
  • cheap snapbacks free
  • cheap toms
  • cheap toms sho
  • cheap toms shoes
  • chrome toolbar
  • coach factory outlet
  • coach outlet online
  • doudoune moncl
  • hollister fran
  • hollister pas
  • http://oakleysunglas
  • http://www.officiali
  • isabel marant
  • isabel marant chauss
  • isabel marant paris
  • Isabel Marant sneake
  • isabel marant wedge
  • lisseur ghd pas cher
  • louis vuitton
  • louis vuitton outlet
  • mulberry pung
  • north face outlet
  • saclouis vuitton
  • snapbacks for sale
  • tn requin pas cher
  • toms shoes out
  • toolbar
  • tory burch flats
  • tory burch outlet
  • tory burch shoes
  • wholesale snapback h
  • wholesale snapbacks
  1. bobsterco
    Member

    Google Chrome 5.0.375.126
    Full RoboForm toolbar Version 1.0.9.51
    RoboForm is 6.10.0

    When I upgraded to
    Full RoboForm toolbar Version 1.0.9.51 and RoboForm is 6.10.0

    Tab switching with my mouse stopped working.

    The "tab switching with my mouse" has either my mouse's Logitech SetPoint SW
    or an AutoHotkey script send ctrl+PgUp or ctrl+PgDn to change tab.

    When it is failing, chrome switches to the adjacent tab very very briefly, then
    returns to the original tab.

    Disabling the extension Full RoboForm toolbar Version 1.0.9.51 resolves the
    problem but also removes roboform. (Not acceptable)

    Re-enabling the RF extension brings the problem back.

    Have tested with the RF extension as the only enabled extension and it still
    fails, so I am not exploring interactions with other extensions.

    The same keystrokes from the keyboard never show the problem.

    Since the problem is present when the keystrokes are sent from either my
    AutoHotkey script, or the mouse's SetPoint software, I am not treating my script
    or Setpoint as a suspect in this crime.

    Help, please.

    Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.