mirror of
https://github.com/YouG-o/YouTube-No-Translation.git
synced 2026-04-25 10:05:54 +03:00
[GH-ISSUE #55] Issue: Extension settings changes not being applied from its menu #51
Labels
No labels
ToDo
bug
enhancement
enhancement
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/YouTube-No-Translation#51
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CrusheerPL on GitHub (Jul 4, 2025).
Original GitHub issue: https://github.com/YouG-o/YouTube-No-Translation/issues/55
Description
As in the topic - cannot apply extension settings changes from its menu. Discovered this issue while looking for a cause of another problem (translated chapters when shouldn't).
Steps to Reproduce
Expected result:
Settings have been applied.
Actual result:
Settings haven't been applied.
Environment
Example Video
The issue has been reproduced in this video: https://youtu.be/UORJ-9fFXow
Extension Settings
Other YouTube-related extensions you are using
uBlock Origin, SponsorBlock
@YouG-o commented on GitHub (Jul 4, 2025):
I don't have the issue on my side. The simpliest way for you is to uninstall and reinstall the extension, it will work again. But I need to know why it happened so before, please do this :
In firefox go to : "about:debugging" in the url bar
Then go to "This Firefox" on the left.
Search for the "YouTube No Translation" in Extensions, and click Inspect.
In the console type :
and send me the result. It will help me understand what's wrong with your settings.
Thank you.
@CrusheerPL commented on GitHub (Jul 4, 2025):
That's weird...

@YouG-o commented on GitHub (Jul 4, 2025):
Thanks for this, I see some missing settings. I just released v2.6.0, it should prevent your issue. If you did not uninstall/reinstalled yet, try to force update and tell me if it fixed it.
Sorry, this issue is 100% my bad.
@CrusheerPL commented on GitHub (Jul 4, 2025):
Reinstalled the extension, everything visually works but I still see the video chapters still got automatically translated.. Anyway, thanks
@YouG-o commented on GitHub (Jul 4, 2025):
Strange, I tried to go on the video you were watching on your video (btw just realised you recorded your issue sorry), changing my YT to Polish and chapters are replaced by the originals on my side.
Just in case : for chapters, you need to have the 'description' feature enabled since the add-on get chapters name in videos descriptions.
Do the other features are back (titles, audio tracks..) ?
Anyway, at least the settings issue should be fixed. Don't hesitate to open a new issue if you still encounter problems with chapters tomorrow (meaning after a fresh restart of your browser and youtube tabs).
@CrusheerPL commented on GitHub (Jul 4, 2025):
Titles worked before and work now. Audio track was always set to original and is now. Chapters - turned on the Description option, deleted youtube cookies, ran a new browser's instance, result the same.
@YouG-o commented on GitHub (Jul 4, 2025):
Is it just the chapters, or also the description that is still translated?
@CrusheerPL commented on GitHub (Jul 4, 2025):
Descriptions are in the original language as should. But i discovered these weird things: chapters are being displayed translated until video playback ends, as shown in this video https://youtu.be/OzSwC_gKYdU
Anyway, thanks for this extension, u make a piece of great job. I'll look forward for the chapters update (and sorry for my english lol)
@YouG-o commented on GitHub (Jul 4, 2025):
Oh I see. Never happened to me, this is weird. I'll have a look tomorrow if I can reproduce it on my side and find a fix. Thanks for the infos
@CrusheerPL commented on GitHub (Jul 26, 2025):
Accidentally found a culprit, it's a SponsorBlock. With that addon disabled, everything works right.
@YouG-o commented on GitHub (Jul 26, 2025):
Thanks for letting me know. I'll have a look to see what cause this conflict and try to fix it so both addon can run together.