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

Jump to bottom

Follow up: Get rid of pdfium manifest patch #8060

Open

yrliou opened this issue Feb 4, 2020 · 0 comments

Labels

dev-concern release-notes/exclude

Projects

Chromium Rebasing

Member

yrliou commented Feb 4, 2020 •

edited

Remove the manifest patch added by brave/brave-core#4500.

SanitizeContentSecurityPolicy for adding brave-resources into csp if chrome-resources is allowed.
chromium_src override of chrome/common/initialize_extensions_client.cc for ChromeExtensionsClient -> BraveExtensionsClient, then add brave-resources in GetPermittedChromeSchemeHosts.

yrliou added dev-concern release-notes/exclude labels

yrliou mentioned this issue

Fix PDF by adding required brave-resources permissions #4500

Merged

7 of 32 tasks complete

rebron changed the title ~~Follow up: Get ride of pdfium manifest patch~~ Follow up: Get rid of pdfium manifest patch

bsclifton added this to Needs triage in Chromium Rebasing via automation

bsclifton moved this from Needs triage to PENDING - patch cleanup in Chromium Rebasing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

You can’t perform that action at this time.