Permission popup appears in wrong position |
|||||||||||||||||||
Issue descriptionChrome Version: 67.3396 OS: Windows 10 I can only seem to reproduce this on a multi-monitor system. What steps will reproduce the problem? (1) Enable Fill-on-Account-Select (chrome://flags#fill-on-account-select) (2) Restart Chrome and put it on the "second screen" (3) Visit a login page for which you've saved credentials (e.g. click "Login" on https://affiliate-program.amazon.com Observe: The password manager popup appears in the wrong position; (it appears to be rooted at 0x0 of the content area) Please use labels and text to provide additional information. If this is a regression (i.e., worked before), please consider using the bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help us identify the root cause and more rapidly triage the issue. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Apr 17 2018
,
Apr 17 2018
Seb, Fabio, any chance this could be related to your work on improving the popups?
,
Apr 20 2018
Sorry I didn't see this email when it was sent. Does the behavior change if you enable/disable chrome://flags/#enable-autofill-native-dropdown-views ?
,
Apr 20 2018
Hi! I've done a bit of investigation on this and I don't think this is related to our recent work. Here is my guess: This doesn't happen when the form has both username and password fields. For example on twitter.com It happens if a username was selected by default. My guess then is that the dropdown wants to show right under the username field, but doesn't find it. So it gets shown at (0,0) I can also only repro this for passwords, not for cards and addresses, since for those two you need to click/focus on a field to trigger. battre@, could you triage on your side?
,
Jul 10
Hi Vasilii. Can you please take a look at this? We've received reports from other users mentioning something similar (see crbug.com/246468#c20 ).
,
Jul 10
As I mentioned in crbug.com/246468#c18 , just one different info from this thread: after a 2nd click on the html input box, the combo re-appear on the right place.
,
Jul 12
We don't actively work on #fill-on-account-select and the flag is off by default. I am pretty sure that this is not a UI issue but rather renderer failed to correctly detect form position. Moving to dvadym@ to decide what to do with this bug.
,
Jul 12
We don't have any plans to launch this feature. I'll leave this bug in our team queue in case if we decide to launch it. It's hard to fix similar bugs because it's hard to detect field visibility in Blink and as result pop-up may be shown in a random place. That's one of the blockers for launching it.
,
Jul 12
Sorry, I can't understand why you (dvadym) is calling this a feature! This is a bug, this is working normally/correctly some weeks ago! In the meantime, I just tested in Chrome Canary and it works!!! Version 69.0.3489.0 (Official Build) canary (64-bit)
,
Jul 12
rbcampacci@: since the feature is disabled for all users, you should no longer see the bug in more recent versions.
,
Jul 12
Strange, for me, the flag chrome://flags/#enable-autofill-native-dropdown-views is "Default". When I changed to disabled, the problem keeps the same. When I changed to enabled, the problem is solved. Back to default, brings back the problem. In Canary, the problem happens at the same way (disabled=problem, enabled=ok), but default probably means the opposite, then, it works! So, temporally, I will leave the flag to enable, waiting by the new version!
,
Jul 12
Do you have chrome://flags#fill-on-account-select enabled? If no, then I'm worried.
,
Jul 12
Can you please double check if chrome://flags#fill-on-account-select is enabled for you? I remember being able to reproduce this only when it was enabled. -------------------------------------------------------------- Side note on native dropdown views: Flag chrome://flags/#enable-autofill-native-dropdown-views enables the new Autofill dropdown. The feature was completed on M68, which is the current beta, so it's safe to turn it on there (and please let us know if you see any bugs). So, before M68 become your stable version (should happen in 2-3 weeks), enabling the flag on your stable Chrome can make it unstable. Enabling on the current Canary/Dev/Beta today is safe. Default for the feature today means it depends on which experiment group you are. It's enabled for 50% on Canary/Dev/Beta, so "default" for you seems to mean "disabled". "Enabled" for you will be safe on M68+.
,
Jul 12
Sure, initially, my flag was default. Enabling it, it works fine. See files attached.
,
Jul 13
Ad #17 -- please note that #15 and #16 ask about chrome://flags#fill-on-account-select, while your screenshots in #17 list only chrome://flags/#enable-autofill-native-dropdown-views. (Also, my apologies, I accidentally deleted your last screenshot by mis-clicking in the page. crbug.com does not seem to provide any undo for that, so I could not fix that.)
,
Jul 13
Sorry, I didn't see you asked about another flag status! For me, it is on "Default". Below you have my tests with all posibilities! chrome://flags#fill-on-account-select - Default chrome://flags/#enable-autofill-native-dropdown-views - Default Wrong place chrome://flags#fill-on-account-select - Enabled chrome://flags/#enable-autofill-native-dropdown-views - Default Right place chrome://flags#fill-on-account-select - Disabled chrome://flags/#enable-autofill-native-dropdown-views - Default Wrong place chrome://flags#fill-on-account-select - Disabled chrome://flags/#enable-autofill-native-dropdown-views - Enabled Right place chrome://flags#fill-on-account-select - Disabled chrome://flags/#enable-autofill-native-dropdown-views - Disabled Wrong place chrome://flags#fill-on-account-select - Default chrome://flags/#enable-autofill-native-dropdown-views - Enabled Right place chrome://flags#fill-on-account-select - Default chrome://flags/#enable-autofill-native-dropdown-views - Disabled Wrong place chrome://flags#fill-on-account-select - Enabled chrome://flags/#enable-autofill-native-dropdown-views - Disabled Wrong place chrome://flags#fill-on-account-select - Enabled chrome://flags/#enable-autofill-native-dropdown-views - Enabled Right place
,
Jul 13
Let's settle on #fill-on-account-select - Disabled #enable-autofill-native-dropdown-views - Disabled You should not see any pop up on page load. Do you see it in the wrong place once you click in the field? Is it only on Amazon?
,
Jul 13
Yes, you are right. I missed that. Setting that (disabled/disabled), on page load, I cant see any popup. After 1st click on input box, the popup appears in the wrong place, after the 2nd click, appear in the right place. I realized amazon page doesnt have a password field, then tested again using an intranet tool. Fill Disabled / Views Enabled - Rigth Place, appear just after 1st click Fill Disabled / Views Disabled - Wrong Place, appear just after 1st click Fill Disabled / Views Default - Wrong place, same as Disabled / Disabled Fill Enabled / Views Enabled - Rigth Place, appear on page load Fill Enabled / Views Disabled - Rigth Place, appear on page load, but "flicked" in the wrong place before! Fill Enabled / Views Default - Right place, same as Enabled / Disabled Fill Default / Views Default - Wrong place, same as Disabled / Disabled Fill Default / Views Enabled - Rigth place, Same as Disabled / Enabled Fill Default / Views Disabled - Wrong place, same as Disabled / Disabled
,
Jul 16
I tested 67.0.3396.99 (Official Build) (64-bit) on Win. On https://rsolomakhin.github.io/autofill/ the bug isn't reproducible with either views on/off. Also I tried amazon.com without luck. Do you observe the bug on the testing page? (https://rsolomakhin.github.io/autofill/)
,
Jul 16
I reproduce the problem, views = disabled and chrome://flags/#fill-on-account-select default or enabled.
,
Jul 19
Strange. As we are launching the views the bug is going away in M69. Do you maybe have some non-default settings on windows like scale, monitors?
,
Aug 2
Sorry for the delay! I use 2 monitors! The problem only happen in windows moved from 1st monitor to 2nd monitors. Windows opened in the 2nd monitor dont have the problem. And I just see the problem in another popups, like show flash, show notifications etc (see attached file).
,
Aug 3
M69 is now in beta. Maybe you could test if you still have those UI problems with the default flags there?
,
Aug 3
Same problem with Canary: Version 70.0.3511.1 (Official Build) canary-dcheck (32-bit)
,
Aug 3
All popups again?
,
Aug 3
At least Popup for notifications are in the wrong place. Autofill (in smoke test mentioned above) is working fine. Do you have any smoke test for this other kind of popups?
,
Aug 6
This is the page for testing permissions https://adrifelt.github.io/demos/page-info-demo.html As the autofill drop-down is obviously fixed but the permission prompt isn't, I'm reassigning the bug to benwells@ for triaging.
,
Aug 6
Thanks! Any questions, contact me!
,
Nov 29
vabr going hobby only -> reducing involvement. Please contact me directly in urgent matters. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by elawrence@chromium.org
, Apr 16 2018Summary: Credential autocomplete popup appears in wrong position (was: Credential autocomplete popup appears in wrong position (multi-mon))
7.8 KB
7.8 KB View Download