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

Test split view bg color in custom theme from web store #27124

Conversation

simonhong
Copy link
Member

fix brave/brave-browser#43052

Screenshot 2025-01-06 at 3 31 52 PM Screenshot 2025-01-06 at 3 33 45 PM Screenshot 2025-01-06 at 3 33 53 PM Screenshot 2025-01-06 at 3 35 24 PM Screenshot 2025-01-06 at 3 37 07 PM

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 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:

fix brave/brave-browser#43057

This is regression from #27008

`nala::kColorDesktopbrowserTabbarActiveTabVertical` and
`nala::kColorDesktopbrowserTabbarHoverTabVertical`
didn't work for private/tor window.

Fixed by setting different colors for above in private/tor theme.
@simonhong simonhong self-assigned this Jan 6, 2025
Comment on lines +41 to +48
mixer[kColorBraveSplitViewTileBackgroundHorizontal] = {
is_toolbar_dark ? nala::kColorPrimitiveNeutral10
: nala::kColorPrimitiveNeutral80};
mixer[kColorBraveSplitViewTileBackgroundVertical] = {
kColorBraveSplitViewTileBackgroundHorizontal};
mixer[kColorBraveSplitViewTileDivider] = {
is_toolbar_dark ? nala::kColorPrimitiveNeutral20
: nala::kColorPrimitiveNeutral90};
Copy link
Member Author

Choose a reason for hiding this comment

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

As these colors are our own color, custom theme doesn't have color for them.
@aguscruiz what I test here is picking similar color of toolbar between our light/dark theme colors for split view tile bg color.
You can see the some screenshots with downloaded custom theme from webstore.
Or, maybe we need to generate when custom theme is used?

Copy link
Collaborator

Choose a reason for hiding this comment

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

image

In these two screenshots the theme is dark but the color being used for active tabs and split tabs are the light ones. So, in those cases, the color theme the user chose independent of wether they have light/dark mode in the browser. Just tested it myself to confirm that.

Let me see how I can solve that split view bg being bad. We'll need a custom solution here, like you suggested

@simonhong simonhong force-pushed the fix_private_window_vertical_tab_color branch from 4834fd8 to 689e490 Compare January 7, 2025 01:24
@simonhong
Copy link
Member Author

Closed and will handle regression issues by #27008 at #27123

@simonhong simonhong closed this Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants