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

Tab separator becomes 1dp wide #1449

Merged
merged 1 commit into from
Jan 25, 2019
Merged

Tab separator becomes 1dp wide #1449

merged 1 commit into from
Jan 25, 2019

Conversation

petemill
Copy link
Member

Fix brave/brave-browser#3081

I kept the patch in for drawing the separators with rounded rectangles because, although extremely subtle, it matches the similar strategy for other separators in Brave (e.g. brave actions bar in location bar).

image

Submitter Checklist:

  • Submitted a ticket for my issue if one did not already exist.
  • Used Github auto-closing keywords in the commit message.
  • Added/updated tests for this change (for new code or code which already has tests).
  • Verified that these changes build without errors on
    • Windows
    • macOS
    • Linux
  • Verified that these changes pass automated tests (npm test brave_unit_tests && npm test brave_browser_tests) on
    • Windows
    • macOS
    • Linux
  • Ran git rebase master (if needed).
  • Ran git rebase -i to squash commits (if needed).
  • Tagged reviewers and labelled the pull request as needed.
  • Request a security/privacy review as needed.
  • Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone

Test Plan:

  • Open multiple tabs
  • Tab separators should be 1dp thick (2px on most retina screens)
    • Take screenshot
    • Zoom in
    • Count pixels

Reviewer Checklist:

  • New files have MPL-2.0 license header.
  • Request a security/privacy review as needed.
  • Adequate test coverage exists to prevent regressions
  • Verify test plan is specified in PR before merging to source

@petemill petemill self-assigned this Jan 24, 2019
@petemill petemill merged commit 6716dc5 into master Jan 25, 2019
@petemill petemill added this to the 0.62.x - Nightly milestone Jan 25, 2019
SK_AlphaOPAQUE));
};

+ const int separator_radius = separator_bounds.leading.width() / 2;
+ // Even if |separator_radius| becomes 1 native pixel the 'roundedness'
Copy link
Collaborator

Choose a reason for hiding this comment

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

we should avoid comments in patches. Any info should be in the commit message or PR and can be found with git blame

Copy link
Member

Choose a reason for hiding this comment

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

I'm ok either way but just noting that I don't think it costs extra time to rebase because of it.

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.

Tab separator is too thick
3 participants