-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Remove unsupported components in brave://components #8709
Remove unsupported components in brave://components #8709
Comments
I am looking into this issue because it needs to be implemented before my fix for #10464 can be merged. @jumde suggested we remove those components that appear with version
On Android, Brave stable 1.17.74 has the above components at
|
An interesting first finding is that Chromium's source code doesn't mention the IDs I quoted above, except in comments. For example
Per https://chromium.googlesource.com/chromium/src/+/lkgr/components/component_updater/README.md, the string It would be nice to have an implementation for blacklisting unwanted components in Brave that simply keeps a list of the string ids |
Looks like this might be broken. I checked the latest nightly ( |
I'm looking into it. From what I see so far, it appears as if the override in Brave that should prevent the components from being installed does not get called. The override blocks unwanted components by their ID. I already ruled out that those IDs have changed. Will update here as I obtain more info. |
The override is called, even with the correct component IDs, but fails to identify them as disallowed. Still investigating. |
Fixed in brave/brave-core#7496. @fmarier you could test the binaries there if you like. |
Checked in Nightly v1.20.48 that my fix in brave/brave-core#7496 worked. On Linux with an empty profile, the components are not there: |
It works for me too (Nightly). Thanks for the follow-up fix! |
Sure. Sorry for the initial bug. |
@fmarier @mherrmann @jumde I'm still seeing the following components from #8709 (comment) listed on brave://components in 1.20.x, however I believe this is expected per other issues in this milestone, correct?
|
@LaurenWags - That is correct. |
Verified passed with
Verified components listed in #8709 (comment) are not shown on brave://components except for:
All components listed on brave://components have non-zero version numbers: Verification passed on
Verified components listed in #8709 (comment) are not shown on brave://components Verification passed on
Verified components listed in #8709 (comment) are not shown on brave://components except for:
All components listed on brave://components have non-zero version numbers: |
@fmarier @mherrmann @jumde In Windows 10 x64 - Dev build |
I'm not sure why it's not avaiable on Mac because I can also see it on Linux, but it is supposed to be enabled: https://bravesoftware.slack.com/archives/C8MP8ME4C/p1607477451338100?thread_ts=1607461532.330600&cid=C8MP8ME4C I added it to the list on https://github.com/brave/brave-browser/wiki/Brave-Components. |
@jumde do you see |
No |
Description
Components like MEI preload, Legacy TLS Deprecation Configuration and Origin Trials are not supported by Brave. We should clean up the list to only list components supported by Brave.
Steps to Reproduce
Actual result:
Unsupported components are displayed.
Expected result:
Should not be displayed
Reproduces how often:
Easily
Brave version (brave://version info)
1.4.96 Chromium: 80.0.3987.132 (Official Build) (64-bit)
Version/Channel Information:
All Channels
The text was updated successfully, but these errors were encountered: