My password manager's inline suggestions stopped appearing on login fields, but the keyboard shortcut still fills them. Extension or browser?

Before you diagnose anything: open the extension's own autofill settings and look for an option along the lines of display suggestions when the icon is selected.

When that is switched on, the suggestion menu no longer opens when you click the field. It opens when you click the small vault icon inside the field. From the outside that is indistinguishable from "inline autofill has stopped working", because the thing you have done for years — click field, get menu — now produces nothing at all.

Switch it off, click a username field, and you will know within five seconds. It costs nothing and it is reversible.

Why this one is so widely misdiagnosed is the part actually worth taking away. Look at your list: reinstall the extension, clean profile, disable the browser's blocking. Every one of those targets state stored in the browser. An extension setting like this is attached to your account and syncs down, so a fresh install pulls it straight back and a clean profile arrives with it already applied. The three most obvious tests all quietly reproduce the cause instead of eliminating it, and each clean result pushes you further towards blaming the browser.

That is also why these threads get so long. The people who happen to have the toggle on and the people with a genuine browser problem describe exactly the same symptom, so the reports pile into one place and neither group's fix works for the other.

If the toggle is already off, then you are in the second group and the rest of the answers here apply.

If the setting is not it, here is the sequence that actually separates the two. Run it in this order, because each step is cheaper than the one after it.

1. Same extension, different browser. You have already done this and it works elsewhere. That rules out the extension's logic being broken — the code that decides what to suggest is fine. It does not rule out the extension, because the part that draws an overlay on top of a page is the part most exposed to how a given browser renders things.

2. Same browser, different password manager. This is the step people skip and it is the one that carries the most information. Install any other manager with an inline-suggestion feature and try one login field. If it is also missing, the browser changed something about that surface and no extension-side fix exists. If the other one works, the fault is in the interaction between your extension and this browser, and the extension's authors can fix it without waiting for the browser.

3. Find the boundary. Note both version numbers — browser and extension — then find the last combination that worked. "It broke last Tuesday" identifies nothing on its own, because browsers and extensions both update themselves silently and often in the same week. Two things changed; only the version numbers tell you which.

That third point is where most of these threads come apart. Someone reports it started at browser version X, and it did, for them. Someone else's extension had updated the day before and they never looked. Both post the same sentence and the thread now contains two incompatible timelines that nobody can reconcile.

On the downgrade question specifically, because you were right to hesitate.

Rolling a browser back is a security decision, not a convenience one. You would be choosing to run a build that is missing every fix shipped since it, on the machine where your vault is unlocked and in the application that renders untrusted pages all day. Browser releases are, to a large extent, security releases. Trading that away to get a menu back — while a working keyboard shortcut sits right there — is a bad trade, and it is a worse one the longer you leave it, because a downgrade quietly becomes permanent when the pinned version stops being top of mind.

The other thing worth knowing is that a thread like this almost never describes one problem. You will typically find the settings explanation, a group who genuinely had a broken build and were fixed by the next release, and a slow trickle of people reporting it again on much later versions where neither story fits. They are not all the same fault, so "this fixed it for me" three comments up may be answering a different question than the one you have.

My suggestion is the boring one: stay current, use the shortcut, and check again after the next couple of updates.

And there is a small consolation in the meantime. An explicit keystroke is a slightly better habit than a menu that appears whenever a page presents something field-shaped, because the decision to fill is yours rather than a response to what the page put in front of you. It is not a reason to want the menu gone, but if you are stuck without it for a fortnight, you are not being made less safe.

One more data point that is useful for narrowing it, and one thing to rule out.

When this comes up, the same symptom shows up on Windows, macOS and several Linux distributions at once, on the same browser version. That is worth treating as evidence rather than noise: something identical across all three is not a packaging problem, so the usual platform-specific advice — reinstall the package, try the other package format, clear the profile directory — is a dead end. Do not spend an evening there.

The thing to rule out is the site rather than either program. A fair number of login pages have moved to asking for the username first and rendering the password field only after you submit it. If the menu used to appear because both fields were present on load, it genuinely will not appear the same way on a two-step form, and the change was the site's. Test on two or three unrelated logins before concluding anything — including one you have not visited in months, since that removes any saved-state explanation as well.