Thanks for the report.

The page is being difficult here. It places an input=text field over the input=password field, and keeps the password field as display:none unless it is focused _and_ the mouse cursor is over it.

Chrome does the right thing with hiding the pop-up as soon as the password field becomes invisible. To the user this does seem confusing, because pixel-wise the rendered page does not change with the password field disappearing.

(Also, Chrome is not autofilling here in case the credentials were saved for www.economist.com, because this is a different origin (subscriptions.economist.com). Chrome understands that these two sub-domains are related, and offers filling on explicit user request. That's a security feature and working as intended as well.)

The reason why Chrome does not fill the username is likely because of the confusing and disappearing text field overlapping the password field.

You can use keyboard to select the password in the pop-up without the mouse leaving the password field. That will allow you to fill it in.

I'm closing this as WontFix, because really this is the website being broken. Special-casing Chrome to cope with such mess would only likely introduce subtle bugs elsewhere. Ideally we would persuade economist.com to adopt sane authentication UI practices like https://www.chromium.org/developers/design-documents/form-styles-that-chromium-understands, but such approach won't scale either. Our bet is in partnering with popular sites on doing the right thing and having others like economist.com learn from them.