Refactor TabStrip bounds calculations in the various browser frame views on all platforms |
||||
Issue description- There are multiple GetTabStripLeftInset() and GetTabStripRightInset() in all those views and they don't override functions with the same names in the base class. - The names Left/RightInset may not be the most appropriate ones. The LeftInset for example is used to be the X coord of the tabstrip. - We also have GetBoundsForTabStrip() overrides in all those views. - Some code is shared and can be unified. I started a minor refactor in this CL https://chromium-review.googlesource.com/c/chromium/src/+/956809. However, it's better to make a follow-up CL handling the above points.
,
Mar 9 2018
(Note, those two suggestions were meant to be mutually exclusive ideas)
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Sep 13
We should try to do this as part of tech debt reduction.
,
Nov 22
|
||||
►
Sign in to add a comment |
||||
Comment 1 by afakhry@chromium.org
, Mar 9 2018