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.

Sign up for GitHub

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
Open

Follow up: Get rid of pdfium manifest patch #8060

yrliou opened this issue Feb 4, 2020 · 0 comments
Labels
dev-concern release-notes/exclude
Projects
Chromium Rebasing

Comments

@yrliou
Copy link
Member

yrliou commented Feb 4, 2020 •
edited

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

from @bridiver

  1. SanitizeContentSecurityPolicy for adding brave-resources into csp if chrome-resources is allowed.
  2. chromium_src override of chrome/common/initialize_extensions_client.cc for ChromeExtensionsClient -> BraveExtensionsClient, then add brave-resources in GetPermittedChromeSchemeHosts.
@yrliou yrliou mentioned this issue Feb 4, 2020
Merged
32 tasks
@rebron rebron changed the title Follow up: Get ride of pdfium manifest patch Follow up: Get rid of pdfium manifest patch Feb 6, 2020
@bsclifton bsclifton added this to Needs triage in Chromium Rebasing via automation Feb 18, 2020
@bsclifton bsclifton moved this from Needs triage to PENDING - patch cleanup in Chromium Rebasing Feb 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
dev-concern release-notes/exclude
Projects
Chromium Rebasing
  
BACKLOG - refactor / patch cleanup
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yrliou