-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension active despite being disabled in extension settings #197
Comments
This issue also happens to me (Win10, firefox103, 5.1.2, with 21:9 screen), setting the video alignment still work after I choose "Never" on "Enable This extension". |
I've played around with it again after. From what I can tell it remains active on the youtube tab/session after switching from enabled to disabled. That persists while browsing youtube, through playlists and autoplay (giving the appearance of persisting on page load). It does not persist on loading YT on a new tab. Attached (in txt because github doesn't like json): It feels like it saves the disabled setting, but only reads that change when opening YT in a new tab, rather than immediately/on video load. |
I would assume it is due to youtube not fully reloading when navigating within the page. As mentioned it only persist while navigating within youtube. A partial reload through F5 does disable the extension. being aware of that I don't consider it a significant issue. but it will be useful to keep in mind that youtube's internal navigation seems to not fully reload the settings. |
In my case, Reload through F5 doesn't disable the extension. The video alignment still effect. |
@Amadeus-AI hi,
Thanks in advance. |
firefox 104 / win10 yes, the issue persist in a new tab |
Shortcuts edit video aspect ratio despite the extension being disabled in Extension settings
To Reproduce
Opened Youtube and disabled the extension. Problem persist on page reloads.
Expected behavior
The Extension should not interact with the open page unless activated
Browser and OS
Additional info
The text was updated successfully, but these errors were encountered: