Forum Discussion
Minimize / Restore / Close button is on unnatural position.
tomscharbach Fedora project... I forgot about that. I run mine from the Chromium site with a third party auto updated tied into a task scheduler to update three or four times a day. I'll have to try out the other modified built of Chromium too. https://chromium.woolyss.com/
Come to think of it, I think I'll go into Windows Sandbox and see how the icons look in Opera which is also built off of Chromium.
You already did Firefox so that base is covered.
Opera' is centered (although their three icons are larger though):
- tomscharbachSep 15, 2019Bronze Contributor
Anthony The current stable build of Chromium for Windows is offset, but only slightly so:
The offset is much less than the offset in Edge Chromium, though, which makes me wonder.
Oh well, enough time wasted in nerd heaven for one day.
- AnthonySep 15, 2019Iron Contributor
tomscharbach Yeah the offset in Chromium isn't that bad, almost not noticeable. My above picture was from Chromium v. 79.0.3914.0 (Build 696689). Edge just needs a minor adjustment of centering.
I don't know how accurate this is, but when I run Edge Canary (78.0.276.0) through the whatversion.net/chrome site and the other Chromium site I listed about it comes up as actually being 78.0.3904.0. Which puts Edge Canary on the level of Chrome Dev in version comparison.
- tomscharbachSep 16, 2019Bronze Contributor
Anthony We can see how this issue developed by looking at Chromium screenshots over the years.
Generalizing the design iterations into three rough periods of Chromium development, I found this:
It looks like the tabs are located in a container within a header container (or perhaps layers -- I haven't looked at the source code), with the height of the header container/layer and the offset of the Minimize/Windowed/Close buttons from the top of the header container/layer changing over time.
The current iteration of Edge Chromium seems to have eliminated the margin between the tab container/layer and the header container/layer altogether but not adjusted the offset.
I think that you are right about what needs to be done -- a minor adjustment in offset. It should be simple enough (again, I haven't looked at the source code so it might be more complicated than it seems) so I hope that Microsoft will attend to making the change before release, as some other Chromium builds have done. It looks amateurish as it now is.