Skip to content
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

Some Chrome extensions cannot be removed #86

Open
JoachimHenze opened this issue May 11, 2024 · 5 comments
Open

Some Chrome extensions cannot be removed #86

JoachimHenze opened this issue May 11, 2024 · 5 comments

Comments

@JoachimHenze
Copy link

JoachimHenze commented May 11, 2024

System Details

  • OS: WinXP Professional SP3 x86
  • Thorium-legacy Version: Thorium_SSE3_122.0.6261.168_WINXP_x32.zip
  • I started the batch file for Portable mode

Problem

  • Some Chrome extensions cannot be removed. When I do press the Remove button, just nothing happens
  • affected are: Chromium pdf Viewer, Google hangouts, Web Store
  • I am not sure whether it is related, but please notice that those that cannot be removed do also have their on-off-toggle-slider disabled (mentioning that just as an additional information)
    image
@JoachimHenze
Copy link
Author

JoachimHenze commented May 11, 2024

The competing "Supermium" browser is not affected by that issue, (as) it ships more lightweight by default.

@gz83
Copy link
Collaborator

gz83 commented May 11, 2024

@gz83 gz83 closed this as not planned Won't fix, can't repro, duplicate, stale May 11, 2024
@Alex313031
Copy link
Owner

@JoachimHenze Read that comment. Supermium has these extensions, but they are normally hidden (because they can't be removed, and are only used to provide services to the browser). Thorium just unhides them for transparency, and so that they can be debugged. Ungoogled Chromium also does this.

Supermium isn't lighter weight or heavier weight than Thorium. They are about equal.

@Alex313031
Copy link
Owner

Alex313031 commented May 12, 2024

@gz83 I think we should put this behind a flag lol. Too many users keep making issues about this. That way it is hidden by default like Chromium/Chrome, but can still be enabled with a chrome://flags flag.

@Alex313031 Alex313031 reopened this May 12, 2024
@gz83
Copy link
Collaborator

gz83 commented May 12, 2024

@gz83 I think we should put this behind a flag lol. Too many users keep making issues about this. That way it is hidden by default like Chromium/Chrome, but can still be enabled with a chrome://flags flag.

This seems like a good idea, but we need to make sure it doesn't introduce other problems.

@Alex313031

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants