NEW 267051
First call of focus({ preventScroll: true }) on password-related input causes scroll into view
https://bugs.webkit.org/show_bug.cgi?id=267051
Summary First call of focus({ preventScroll: true }) on password-related input causes...
Bruno Stasse
Reported 2024-01-03 10:57:41 PST
Created attachment 469277 [details] testcase When a password-related text input [1] receives focus through focus({ preventScroll: true }) for the first time while being positioned in the area that will be covered by the virtual viewport, it will (wrongly) be scrolled into view. It is expected that { preventScroll: true } prevents all scrolling into view, and it does so in further focus({ preventScroll: true }) calls, or if the input is not password-related. [1] Any text input that Safari identifies as related to passwords, and for which the "Passwords" button will be displayed in the suggestion bar. How to reproduce: - Open the test case - Scroll down enough so the input is positioned in the area that will be covered by the virtual keyboard. - Tap the button. - The input should receive focus and no scroll should occur, resulting in the input being covered by the virtual keyboard. - However, on first try, the input will be scrolled into view; this is the bug. - If you try again without refreshing, no scroll will occur, as expected. - This only occurs with password-related inputs which are not of type "password". Here we simply added a "username" id to the input so Safari identify it as such. If you remove it, you'll notice the bug doesn't occur.
Attachments
testcase (1.91 KB, text/html)
2024-01-03 10:57 PST, Bruno Stasse
no flags
testcase_video (3.81 MB, video/mp4)
2024-01-03 10:58 PST, Bruno Stasse
no flags
Bruno Stasse
Comment 1 2024-01-03 10:58:52 PST
Created attachment 469278 [details] testcase_video Video recording of the testcase.
Radar WebKit Bug Importer
Comment 2 2024-01-10 10:58:17 PST
Bruno Stasse
Comment 3 2024-05-03 05:10:02 PDT
Correction of the description: "covered by the virtual viewport" was supposed to be "covered by the on-screen keyboard". Any update on this bug?
Note You need to log in before you can comment on or make changes to this bug.