Bugzilla

I am able to reproduce this.

However, the symptoms here seem orthogonal to bug 1884807 / bug 1916002 to me. Those bugs addressed cases where, after the keyboard comes up, the input element you're typing into is hidden by the keyboard and **cannot** be scrolled into view.

On this page, the input element **can** be scrolled into view, it just doesn't happen automatically (for some still-to-be-diagnosed reason). Whatever the reason for that, it's unlikely to have been affected by bug 1884807.

(I think that also means this bug does not merit S2 severity: manually scrolling the input field into view is a readily apparent and available workaround.)

I am able to reproduce this.

However, the symptoms here seem orthogonal to bug 1884807 / bug 1916002 to me. Those bugs addressed cases where, after the keyboard comes up, the input element you're typing into is hidden by the keyboard and **cannot** be scrolled into view.

On this page, the input element **can** be scrolled into view, it just doesn't happen automatically (for some still-to-be-diagnosed reason).

(I think that also means this bug does not merit S2 severity: manually scrolling the input field into view is a readily apparent and available workaround.)

I am able to reproduce this.

However, the symptoms here are a bit different from the ones we expect bug 1884807 / bug 1916002 to fix. Those bugs addressed cases where, after the keyboard comes up, the input element you're typing into is hidden by the keyboard and **cannot** be scrolled into view.

On this page, the input element **can** be scrolled into view, it just doesn't happen automatically (for some still-to-be-diagnosed reason).

(I think that also means this bug does not merit S2 severity: manually scrolling the input field into view is a readily apparent and available workaround.)