AutoInput Autoinput causing Chrome Bug

Discussion in 'AutoApps' started by Klark1kent, Nov 8, 2019.

  1. Klark1kent

    Klark1kent New Member

    Joined:
    Mar 15, 2018
    Messages:
    2
    Likes Received:
    0
    I'm putting this here in case others have run into this issue... thankfully this doesn't impact Tasker or other autoapps but Autoinput with accessibility setting ON causes the omnibox in chrome to ignore any chrome://flag or regular menu setting allowing full screen browsing i.e. the address bar to auto hide on scroll. With it on the address bar never hides in Chrome regardless of release, platform, or version.

    See thread

    https://support.google.com/chrome/thread/10143555?hl=en&dark=0
     
  2. Klark1kent

    Klark1kent New Member

    Joined:
    Mar 15, 2018
    Messages:
    2
    Likes Received:
    0
    Also as a side not when posting in the Google forum I was not allowed to post when my comment mentioned Tasker due to its community guidelines. After removing tasker from my comment, I was able to post my reply. Weird.
     
  3. usn.mustanger

    usn.mustanger New Member

    Joined:
    Feb 23, 2016
    Messages:
    12
    Likes Received:
    0
    I can confirm AutoInput causing odd problems with Chrome flags. For example, with the "Enable horizontal tab switcher" enabled along with AutoInput accessibility services, Chrome still only displays the vertical "accessibility" switcher. The horizontal tab switcher only displays when I disable AutoInput in Android accessibility services menu.
     

Share This Page