Bugzilla

OK, I make sense this bug, But this depends on [Autofill compatibility mode](https://developer.android.com/reference/android/service/autofill/AutofillService#compatibility-mode). Although we manage autofill focus by `AutofillDelegate`, this focus is sometime lost unfortunately.  Android OS's compatibility mode layer (`AutofillManager.CompatibilityBridge`) of Autofill listens a11y event, then, when `AccessibilityEvent.TYPE_VIEW_FOCUSED` is received, it calls `AutofillManager.notifyViewOfEnter` with a11y virtual Id.  It means that focus id is changed.

The compatibility mode walks thought the accessibility nodes, so it causes bad performance (bug 1734552).  Most code can disable by override View's method, but there is no way to disable `AutofillManager.CompatibilityBridge` from application.

If we set correct focused id after a11y event, it still has performance issue, and since `onFillRequest` on autofill service  is called several times, autofill UI is shown by several times (it means that this UI causes flicker).

I think that BitWarden should disable compatibility mode since we already support autofill framework. I will send PR to disable it with longVersionCode.  Firefox Nightly seems not to use compatibility mode.

Of course, another workaround is `accessibility.force_disabled=1` by about:config (Beta only).

OK, I make sense this bug. This depends on [Autofill compatibility mode](https://developer.android.com/reference/android/service/autofill/AutofillService#compatibility-mode). Although we manage autofill focus by `AutofillDelegate`, this focus is sometime lost unfortunately.  Android OS's compatibility mode layer (`AutofillManager.CompatibilityBridge`) of Autofill listens a11y event, then, when `AccessibilityEvent.TYPE_VIEW_FOCUSED` is received, it calls `AutofillManager.notifyViewOfEnter` with a11y virtual Id.  It means that focus id is changed.

The compatibility mode walks thought the accessibility nodes, so it causes bad performance (bug 1734552).  Most code can disable by override View's method, but there is no way to disable `AutofillManager.CompatibilityBridge` from application.

If we set correct focused id after a11y event, it still has performance issue, and since `onFillRequest` on autofill service  is called several times, autofill UI is shown by several times (it means that this UI causes flicker).

I think that BitWarden should disable compatibility mode since we already support autofill framework. I will send PR to disable it with longVersionCode.  Firefox Nightly seems not to use compatibility mode.

Of course, another workaround is `accessibility.force_disabled=1` by about:config (Beta only).