-
Notifications
You must be signed in to change notification settings - Fork 839
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
[Settings] Fixes fonts subpage flakiness in search. #23064
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -50,6 +50,14 @@ RegisterPolymerTemplateModifications({ | |
} else { | ||
console.error('[Brave Settings Overrides] People Page cannot find syncSetup/advanced template') | ||
} | ||
const syncSetupPageContent = templateContent.querySelector( | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Q) It's also leftover and could be deleted as we have our own sync page? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, we don't seem to be using this page. It seems to have something to do with the Privacy Guide, which we disable anyway. When using search in settings, if not removed, this template causes an exception because it can't find the trigger control for the page. |
||
'template[is=dom-if][route-path="/syncSetup/pageContent"]') | ||
if (syncSetupPageContent) { | ||
syncSetupPageContent.remove() | ||
} else { | ||
console.error('[Brave Settings Overrides] People Page cannot ' + | ||
'find syncSetup/pageContent template') | ||
} | ||
// always show the template content | ||
signinTemplate.setAttribute('if', 'true') | ||
// remove the google account button | ||
|
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -71,6 +71,11 @@ export default function addBraveRoutes(r: Partial<SettingsRoutes>) { | |||||
} | ||||||
if (pageVisibility.content) { | ||||||
r.BRAVE_CONTENT = r.BASIC.createSection('/braveContent', 'content') | ||||||
// Move fonts from APPEARANCE to BRAVE_CONTENT | ||||||
if (r.FONTS) { | ||||||
delete r.FONTS | ||||||
} | ||||||
r.FONTS = r.BRAVE_CONTENT.createChild('/fonts'); | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How about having
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I personally have no objections. The only thing I wonder if people who are used to going to There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ah, i see. Using current one would be helpful for many users. |
||||||
} | ||||||
if (r.SITE_SETTINGS) { | ||||||
r.SITE_SETTINGS_AUTOPLAY = r.SITE_SETTINGS.createChild('autoplay') | ||||||
|
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.
ditto