-
Notifications
You must be signed in to change notification settings - Fork 896
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
[VerticalTab] Move the new tab button to appear immediately after the last tab #27117
[VerticalTab] Move the new tab button to appear immediately after the last tab #27117
Conversation
b74a8ee
to
75bc6ba
Compare
@simonhong Could you kindly review this PR? |
@jagadeshjai Can you adjust the height of new tab button to 32px like this? and maybe we also want to adjust its hover color? |
Thanks @simonhong for catching that one. Yeah, hover color should be the same as the hover color for tabs |
Just now noticed that @rebron mentioned adding a separator between the tabs and the New Tab button in the issue description
@aguscruiz Can we update the same in design as well? |
fyi, CI gave test failure with this PR. |
The test failure is actually due to this bug. |
03d5d2a
to
5dd5cbb
Compare
0f41677
to
8d79126
Compare
8d79126
to
defb49d
Compare
d611153
to
4d9a5c7
Compare
773297f
to
1b31143
Compare
This PR reveals another bug - brave/brave-browser#43226 |
if (views::View* target_v = TARGET_GETTER; \ | ||
tabs::utils::ShouldShowVerticalTabs(browser_view_->browser()) && \ | ||
(target_v == tabstrip() || !THIS->Contains(target_v))) { \ | ||
ConvertPointToScreen(THIS, POINT); \ |
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.
As this POINT
is from THIS
, we should call ConvertPointToScreen()
with THIS
and POINT
.
… last tab as per the new design. And Keep the new tab button fixed at the bottom when tabs overflow.
Each key of shortcut has its own border.
as it returns max height.
7fb3f5b
to
791df83
Compare
CI looks good for this PR - #27125 |
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 looks good to me, but I'll leave final approval to @simonhong, as he knows a lot more about this code than me 😄
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.
Thanks @jagadeshjai 👍🏼
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.
chromium_src
++
@bsclifton , needs your power :) I think all good to merge now. |
Released in v1.76.19 |
Move the new tab button to appear immediately after the last tab last tab as per the new design.
And Keep the new tab button fixed at the bottom when tabs overflow.
Also this new tab button position change reveals another bug and
VerticalTabStripRootViewBrowserTest.DragAfterCurrentTab
caught it.Converting point from root view to tab strip view was wrong in
chromium_src/chrome/browser/ui/views/frame/browser_root_view.cc
.Resolves brave/brave-browser#42533
Resolves brave/brave-browser#43226
OutCome
Submitter Checklist:
QA/Yes
orQA/No
;release-notes/include
orrelease-notes/exclude
;OS/...
) to the associated issuenpm run test -- brave_browser_tests
,npm run test -- brave_unit_tests
wikinpm run presubmit
wiki,npm run gn_check
,npm run tslint
git rebase master
(if needed)Reviewer Checklist:
gn
After-merge Checklist:
changes has landed on
Test Plan:
See the linked issue.