translate-tools/linguist

Translation of a website with a .notranslate class on the HTML element

Open

#591 opened on Oct 22, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (50 forks)auto 404
RFChelp wanted

Repository metrics

Stars
 (1,033 stars)
PR merge metrics
 (PR metrics pending)

Description

I’ve noticed some strange behavior:

The site adds a .notranslate class to the HTML element. When I translate the site, I do not see the translated text — that part works as expected. When i select some text the translation button to not appear, and this expected behavior, because the page in translated state.

But like a user who did not know about .notranslate selector i think the extention not work. I translated the page but didn’t see any translation. Then I selected the text, but the translate button didn’t appear either.

Image

Contributor guide

Research direction
Examine the extension's content script logic to understand how it handles the .notranslate class on the HTML element. Identify where the translation visibility and selection button triggers are suppressed. Consider adding an override option or a visual indicator to inform users when translation is blocked by .notranslate.
Tech stack
javascripttypescript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitBasic understanding of browser extensions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60