Immersive Translate Translating Input Boxes or Skipping Forms? Field Rules and Exclusion Checks

When Immersive Translate translates input boxes—or a form area never moves—split mis-scanned editable fields from a dead install. For field faults, enable “skip inputs / form fields,” tighten never-translate and selector excludes, hard refresh, then retest; read adjacent help with selection translate instead of disabling every skip. Body text OK and only fields weird → stay on field rules; gray icons or silence everywhere → not-working track.

People searching for Immersive Translate input fields or form field translation usually already get paragraph translations—the pain is placeholders flipping language, labels injecting bilingual nodes into search chrome, or admin form help that never moves. That is a different layer from “click Translate, nothing happens,” which belongs in the not-working checklist. Unclear package lineage starts at the download page. Overlap or covering text → bilingual display article. Full page fine but selection missing → selection popup fixes. This post stays on what to skip vs translate inside forms.

Input glitches vs not working

Field-problem signals: article paragraphs translate, but labels beside input / textarea get bilingual inserts, placeholders rewrite, editable carets jump—or help copy inside a form shell stays frozen while other columns work.

Not-working signals: gray icon, no response, silence on every host, options will not open—load/conflict/permission territory in the not-working checklist.

Compare: clean profile, Immersive Translate only, one static English page with a search box. Paragraphs OK and only the box misbehaves → field rules. No text even on the short page → not-working first; stop editing exclusion lists.

Field rules: translate vs skip

Set intent before flipping global switches:

1. Read-only body, help copy, field label text → usually translate.
2. Live values, passwords, OTP, tokens, draft body → skip, so nothing hits the engine or breaks typing.
3. Placeholders → skip in most workflows; if you need the example sentence, selection-translate that line.
4. Sites nesting labels with editable nodes in one translatable chunk → the extension may send the whole block; use finer skip or site-level exclude.

A trap I hit: a SaaS rendered “Email” as a sibling span next to the input; bilingual mode translated the label and shoved it into the row. Toggling “skip input-related nodes” or making that host manual/translation-only beat disabling the whole extension.

When inputs or placeholders get translated

Tighten in this order:

• Enable “skip inputs,” “do not translate form fields,” “ignore placeholder” (wording varies by version).
• If “translate on open” is on for that host, switch to manual—auto passes love top-bar search boxes.
• Park admin, mail, and banking hosts in never-translate; keep reading sites on the allowlist.
• After changes, close the tab or hard refresh; old pages may still carry the previous inject nodes.

Still wrong: private window with Immersive Translate alone. If only a “beautifier / form enhancer” extension triggers it, disable that conflict first. Stacked glyphs belong in bilingual display—separate from “field text got sent.”

When form copy will not translate

The other complaint: help text inside forms never translates. Confirm the block was not over-skipped:

• Global “skip forms” too broad → briefly disable for a read-only help paragraph, then restore so credential fields stay out.
• Never-translate, URL rules, or CSS selector blacklists hitting /settings, /login, or the form wrapper.
• Copy in an iframe / cross-origin embed → parent moves, child does not; grant the child separately or use selection.

For one sentence, prefer the selection popup instead of “translate every input” for three lines of help. Core bilingual triggers also sit in the webpage translation guide—confirm paragraphs respond manually before polishing field toggles.

Rich text, contenteditable, dynamic forms

Mail drafts, block editors, and admin WYSIWYG are half input, half body:

• Bilingual while editing → inserted nodes steal the caret, break undo, rewrite unsaved drafts.
• SPA forms: inputs rendered after routing may still follow the old policy; wait until the form is stable before deciding translate vs skip.
• Policy: never-translate or click-only on writing hosts; keep auto on reading hosts. Use selection for single words—do not pour the whole page into the editor.

Odd behavior only after client routes belongs with Incognito/SPA timing checks; do not mix “field policy” with “extension never loaded.”

Vs bilingual display or selection faults

Avoid reinstall loops:

• Inputs/placeholders mistranslated, or form help over-skipped → this article: field skip, exclusions, selectors, contenteditable policy.
• Gray icon / silence everywhere → not-working checklist.
• Text appears but overlaps, drifts, or covers → bilingual display fixes.
• Page and field labels OK, selection popup missing → selection popup fixes.
• Phone browser cannot host extensions, or the pain is only narrow-screen forms → read mobile browser options and limits, then return to field rules.
• Unclear package source → verify on the download page, then retest.

Once stable, note which hosts may translate labels and which must skip every form. Cheaper than resetting the extension after every misfire.

FAQ

Translated login box = dead extension?

Usually no. Enable skip-inputs and shrink auto scope; total silence → not-working checklist.

Only one admin form stays original?

Check skip-forms, never-translate, and iframes. Use selection for help lines; restore skip afterward.

Rich-text editor scrambled?

Disable auto bilingual on writing hosts; use selection. Overlap → bilingual display article.

Can password fields be translated?

They should not. Keep password skips; debug on non-sensitive pages only.