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

Reorganize settings webui #20160

Merged
merged 3 commits into from
Sep 14, 2023
Merged

Reorganize settings webui #20160

merged 3 commits into from
Sep 14, 2023

Conversation

simonhong
Copy link
Member

@simonhong simonhong commented Sep 14, 2023

fix brave/brave-browser#32957
fix brave/brave-browser#32990
fix brave/brave-browser#32956
fix brave/brave-browser#32954
fix brave/brave-browser#32955

Resolves

Submitter Checklist:

  • I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
  • There is a ticket for my issue
  • Used Github auto-closing keywords in the PR description above
  • Wrote a good PR/commit description
  • Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
  • Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
  • Checked the PR locally:
    • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
    • npm run lint, npm run presubmit wiki, npm run gn_check, npm run tslint
  • Ran git rebase master (if needed)

Reviewer Checklist:

  • A security review is not needed, or a link to one is included in the PR description
  • New files have MPL-2.0 license header
  • Adequate test coverage exists to prevent regressions
  • Major classes, functions and non-trivial code blocks are well-commented
  • Changes in component dependencies are properly reflected in gn
  • Code follows the style guide
  • Test plan is specified in PR before merging

After-merge Checklist:

Test Plan:

@simonhong simonhong added the CI/skip Do not run CI builds (except noplatform) label Sep 14, 2023
@simonhong simonhong self-assigned this Sep 14, 2023
@rebron rebron changed the title Reorgarnize settings webui Reorganize settings webui Sep 14, 2023
fix brave/brave-browser#32990
fix brave/brave-browser#32956
fix brave/brave-browser#32954

Moved social blocking menu as a shields' sub section.
Moved new tab menu as a get started's sub section.
@simonhong simonhong removed the CI/skip Do not run CI builds (except noplatform) label Sep 14, 2023
@simonhong simonhong marked this pull request as ready for review September 14, 2023 06:15
Copy link
Contributor

@sangwoo108 sangwoo108 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@@ -150,3 +123,32 @@
</settings-subpage>
</template>
</settings-animated-pages>
<div hidden="[[isAdBlockRoute_]]">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

q. I'm curious why this was added. Was it removed accidentally?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This page is used for two screen.

  • brave://settings/shields
  • brave://settings/shields/filters

Above second screen is shown when we click Content filtering option.
Then, isAdBlockRoute_ gives true and we need to hide all except filter subpage(adblck-subpage element).

this.browserProxy_.setMetricsReportingEnabled(enabled);
}

setMetricsReportingPref_(metricsReporting: MetricsReporting) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like this was copied from the upstream code. It might be worth leaving comment about where it's from.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added

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