Compatibility Policy

Compatibility is useful, not universal.

Application portals change their HTML, JavaScript frameworks, validation rules and control implementations. FormFill India therefore treats compatibility as a best-effort, evidence-based feature.

Do not assume support from a domain name. A portal may expose different forms, subdomains or steps with different technical behavior. Always test and review before using the extension on a real application.

Compatibility labels

Label	Meaning
Generic	Common HTML/semantic matching; no site-specific adapter.
Adapter	Site-specific matching/fill logic exists for a known portal pattern.
Manual	The step should be completed manually because reliable automation is not provided.

Current portal notes

SSC

An SSC compatibility path exists for common OTR/personal-details fields and re-entry/verification fields. Portal updates can change behavior.

RRB

RRB remains in the extension as a compatibility-testing path, including a dedicated Quick Fill adapter. Results may be incomplete on dynamic Angular forms and must be reviewed.

Generic forms

Standard text inputs, textareas, selects and radio groups with recognizable labels/attributes are the main generic target.

Dynamic/custom forms

Custom controls, cross-origin frames, protected inputs, site-specific masks and framework behavior can prevent reliable matching or write-back.

Manual boundaries

Passwords, OTPs, CAPTCHA, payment credentials, identity verification and final submission remain manual. Never let an autofill tool replace your own review of an application.