Immersive Translate Selection Popup Missing? Fix Selection and Shortcut Conflicts

Immersive Translate selection mode needs the selection / mouse-translate option enabled, then a real text selection on copyable page content before the selection translate popup can appear. When the bubble never shows, check the feature switch, whether you selected inside an input or a non-selectable region, whether the hotkey is stolen by the OS or another extension, and whether a second dictionary tool is listening to the same selection. Full-page bilingual working with selection dead is common—do not treat it as a broken install. If the popup shell appears without a translation, debug the engine next.

People searching for Immersive Translate selection usually already see the floating control. The stuck moment is: highlight a phrase, and nothing pops. That is a different track from “full page never translates” or a gray icon—those belong in the not-working checklist. This article stays on the selection translate popup: switches, selections, shortcut conflicts, and extension fights. If the install is shaky, start from the download page.

What the selection popup actually depends on

Three things must line up: the extension is allowed on the tab, settings permit selection / mouse translate, and the page produces a real text selection. Miss one, and you get silence after highlighting.

Selection shares the extension process with full-page mode, not the same trigger path. Full-page rewrites DOM from a button or page hotkey; selection waits for a selection change (and sometimes an extra key) to mount a bubble. So bilingual pages with a dead selection path are normal—not proof of a corrupted install.

Baseline on a static English news paragraph: drag 3–8 words. If the baseline fails, open settings; if only one site fails, stay on site scripts and permissions before touching engines. How selection fits next to full-page reading is in the webpage translation guide.

Verify selection translate is on

Labels vary by version. Typical path: extension icon → Settings / Options → find Selection translate, Mouse selection, or similar → confirm it is enabled. If there is a “hotkey-only after select” mode, know whether your build pops on mouseup or needs an extra key.

Save, then hard-refresh the test tab and select again. A trap I hit: changing settings without refresh left the old tab on the old policy, so it looked like the switch “did nothing.”

If site permissions are unclear, confirm the extension can run on the host (especially if “on all sites” was narrowed to click-to-enable) using the browser extension setup guide.

Text selected, still no popup

With the switch on and no bubble, inspect the selection itself:

• Selecting inside <input> / <textarea> / rich editors? Some builds skip editable fields so they do not fight the IME caret.
• Page bans selection (user-select: none, or scripts calling removeAllRanges on mouseup)? Common in embedded PDF viewers and some docs portals.
• Selecting pixels on an image or canvas? No text node means no popup to invent.
• Incognito with the extension disabled for private windows? Icon may show while content scripts never inject.

Compare: same browser, static blog post vs problem site. Static works / site fails → site limits. Both fail → return to switches, permissions, and conflicts.

Shortcut conflicts

If your workflow is “select, then press a hotkey for the selection translate popup,” conflicts look like: selection is fine, the key does nothing—or launches another app.

1. Open the browser extension shortcuts page (Chrome: chrome://extensions/shortcuts; Edge uses edge://; Firefox under Add-ons management).
2. Find Immersive Translate entries tied to selection / translate selection; note “Not set” or duplicates with other extensions.
3. Pick a combo your machine rarely uses (avoid screenshots, IME switches, terminal binds).
4. Save and retest in a new tab—old tabs may keep stale bindings.

OS-level grabs (macOS VoiceOver chords, Win+Shift screenshots, launcher tools) never appear on the extension shortcuts page. Temporarily quit the suspect app and try the selection hotkey again.

Other extensions steal the selection

Two dictionary / translator extensions on the same selection often yield: nobody pops, a flash then cover, or only the other tool’s bubble. Simple Translate, learner dictionaries, and similar selection tools all listen to the same events.

Disable other selection/translate extensions, leave Immersive Translate alone, refresh, retest. Re-enable one at a time to find the clash. If you mainly need lightweight lookup, decide the primary tool with the translation extension picker and keep the rest off.

Custom ad-block rules that hit content-script hosts can also silence selection; allowlist the site briefly and compare.

Not the same as full-page failure

Split tracks:

• Gray icon, full-page and selection both dead everywhere → not-working checklist.
• Full-page works, only the selection translate popup fails → stay here: switch, selection, hotkey, extension fights.
• Popup shell appears but empty/error → custom engine / key / quota, not more hotkey remaps.

Change one variable at a time: disable clashes, then remaps, then engines. Once it works, note which sites need which permission so another extension does not overwrite the habit tomorrow.

FAQ

Selection translate on, still no Immersive Translate popup?

Verify the switch and trigger mode, skip editable/non-selectable regions, and disable other dictionary extensions. If full-page works, skip a full reinstall.

Popup flashes then vanishes—why?

Usually the page clears the selection or steals focus. Compare on a static page; single-site failures point to site scripts or blockers.

Remapped shortcut still conflicts—what next?

Trust the browser shortcuts page, avoid OS and other-translator combos, retest in a new tab.

Popup chrome shows but no translation?

Selection path is likely fine—debug engine/network next; if full-page also fails, use the not-working guide.