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

Investigate whether to enable _google_chrome in grit_defines to minimize patches #502

Open
yrliou opened this issue Jul 7, 2018 · 0 comments
Labels

Comments

@yrliou
Copy link
Member

@yrliou yrliou commented Jul 7, 2018

So far we have seen two kinds of use cases related to _google_chrome, and our solutions usually involve patching html/js files which should be minimized as much as possible.

  1. Use _google_chrome if guard to hide chrome specific UI elements for branding, ex: brave/brave-core#212

  2. Enable UI elements or code blocks which are only available for _google_chrome build, ex: brave/brave-core#220

We should go through all _google_chrome cases in the code base and evaluate whether enabling _google_chrome flag and selectively disabling it only when needed might give us a result of less patches, and revise our implementations accordingly if so.

cc @bridiver

@yrliou yrliou added the enhancement label Jul 7, 2018
@bbondy bbondy added this to Backlog in 0.55.x - Release Jul 7, 2018
@bbondy bbondy added this to the Backlog milestone Jul 7, 2018
@rebron rebron modified the milestone: 1.x Backlog Feb 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.