Chrome Web Store — Reviewer test guide

Transloco Translator · Transloco Protocol v1

Single purpose: Let users select text on allowed websites, enter multilingual translation values, and save them to a user-configured translation API (fixed REST contract). No data is sent to the extension publisher’s servers.

Prerequisites

Step 1 — Install and open settings

  1. Install Transloco Translator from the submitted package.
  2. Click the toolbar icon → Manage connections, or open the extension Options page (opens the connection manager in a tab).

Step 2 — Create a connection

  1. Click + New connection.
  2. API base URL: use your test API, or http://localhost:5080 if running the sample backend.
  3. Site domains (one per line), for example: 
    http://localhost/*
http://127.0.0.1/*
  4. Locales: default includes uz, ru, en — editable.
  5. Custom headers: add Authorization if your API requires auth. For the sample API: value Basic YWRtaW46dHJhbnNsb2Nv (username admin, password transloco).
  6. Click Create / Save.
  7. When Chrome asks for host permissions, click Allow.

Step 3 — Activate and test API

  1. On the connection card, click Set active (if not already active).
  2. Click Test. Success message appears if discovery or API responds; auth errors show if credentials are wrong.

Step 4 — Text selection UI (core feature)

  1. Open a page matching your site pattern (e.g. http://localhost:3000 or any http://localhost/... page).
  2. Refresh the tab after installing or changing the active connection.
  3. Select a word or short phrase with the mouse.
  4. After ~400 ms, a small translation icon appears below the selection (dark square with “A/translate” style icon).
  5. Click the icon. A panel opens showing the key and one input per locale.

Step 5 — Save translation

  1. Enter text for one or more locales (e.g. Uzbek / English).
  2. Click Save.
  3. If the API is reachable: toast Created or Updated. If not: red error toast (UI still works).

Expected behavior on non-configured sites

On domains not listed in the active connection’s site patterns (e.g. https://www.google.com), selecting text should not show the translation icon. This is intentional.

Protocol documentation (optional check)

In the connection manager, the Protocol v1 — for backend developers section includes a Download protocol package button (ZIP with OpenAPI and guides). This is for API implementers, not required for review.

Permission summary for review

Permission Use
storage Connection profiles; auth header values in local storage only.
activeTab + scripting Selection overlay on user-approved site patterns only.
optional_host_permissions User-granted access per connection to call their API and run on their domains.

Copy-paste block (dashboard “Notes to reviewer”)

Install → Manage connections → + New connection.
Site domains: http://localhost/* (or your test origin). Save → Allow permissions.
Set active → Test. Open matching localhost page, refresh tab, select text → icon → form → Save.
Icon must NOT appear on sites outside configured patterns.
Sample API (optional): http://localhost:5080, Authorization: Basic YWRtaW46dHJhbnNsb2Nv
Full steps: https://imadatov.github.io/Transloc-/reviewer-test.html (update URL if repo name differs)