-
Notifications
You must be signed in to change notification settings - Fork 868
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
Support publisher branded site banners #939
Conversation
65267a7
to
bbd37f1
Compare
bbd37f1
to
bf3a138
Compare
Support publisher branded site banners
@NejcZdovc approved uplift to |
@kjozwiak will do thx |
Support publisher branded site banners
} // namespace | ||
|
||
BraveRewardsSource::BraveRewardsSource(Profile* profile) | ||
: profile_(profile->GetOriginalProfile()) {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this is really old, but it's still in the code and we shouldn't be doing this. There is a method to "redirect" webuis to open in regular profiles which is used by settings, etc...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't a WebUI though, it's a URLDataSource. Our code is based off of upstream's favicon data source implementation, which does a similar thing (though maybe that's also problematic): https://source.chromium.org/chromium/chromium/src/+/main:chrome/browser/ui/webui/favicon_source.cc;l=71
Fixes brave/brave-browser#1923
Requires brave-intl/bat-native-ledger#184
Submitter Checklist:
npm test brave_unit_tests && npm test brave_browser_tests
) ongit rebase master
(if needed).git rebase -i
to squash commits (if needed).Test Plan:
Reviewer Checklist: