Home

Minimize / Restore / Close button is on unnatural position.

%3CLINGO-SUB%20id%3D%22lingo-sub-856032%22%20slang%3D%22en-US%22%3EMinimize%20%2F%20Restore%20%2F%20Close%20button%20is%20on%20unnatural%20position.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856032%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20156px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131833iE32EDD2319A84FF0%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22sd.png%22%20title%3D%22sd.png%22%20%2F%3E%3C%2FSPAN%3EThis%20is%20Edge%20Insider's%20position.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20149px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131834iCD457D80B2CC1FA7%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22gf.png%22%20title%3D%22gf.png%22%20%2F%3E%3C%2FSPAN%3EThis%20is%20Chrome's%20position.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdge%20Insider's%20position%20is%20unnaturally%20climbed%20up.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856090%22%20slang%3D%22en-US%22%3ERe%3A%20Minimize%20%2F%20Restore%20%2F%20Close%20button%20is%20on%20unnatural%20position.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856090%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F409115%22%20target%3D%22_blank%22%3E%40HiSky%3C%2FA%3E%26nbsp%3B%20Good%20catch.%26nbsp%3B%20It%20is%20subtle%2C%20but%20the%20buttons%20are%20not%20centered%20vertically%20in%20the%20allotted%20horizontal%20bar%20in%20Edge%20Chromium.%26nbsp%3B%20In%20addition%20to%20the%20comparison%20to%20Chrome%2C%20these%20are%20the%20comparisons%20to%20Edge%20(Classic)%20and%20Firefox%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20552px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131837i01F5329275B999B1%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Min-Win-Close%20Buttons.jpg%22%20title%3D%22Min-Win-Close%20Buttons.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20know%20it%20the%20difference%20is%20intentional%2C%20but%20it%20seems%20to%20me%20that%20vertical%20centering%20would%20be%20preferable%20to%20the%20offset.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856115%22%20slang%3D%22en-US%22%3ERe%3A%20Minimize%20%2F%20Restore%20%2F%20Close%20button%20is%20on%20unnatural%20position.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856115%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F409115%22%20target%3D%22_blank%22%3E%40HiSky%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdge%20insider%20Canary%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20191px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131843i8754AFBE6A60A550%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Annotation%202019-09-15%20171953.png%22%20title%3D%22Annotation%202019-09-15%20171953.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGoogle%20Chrome%20Canary%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20214px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131844i094769D5859DA299%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Annotation%202019-09-15%20172140.png%22%20title%3D%22Annotation%202019-09-15%20172140.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20Edge%2C%20the%20buttons%20look%20like%20they%20need%20to%20be%20moved%20a%20little%20downwards%20but%20that's%20only%20when%20you%20compare%20it%20to%20the%20Google%20Chrome.%3C%2FP%3E%3CP%3E%3CSTRONG%3Eneither%3C%2FSTRONG%3E%20of%20the%20browsers%20have%20their%20buttons%20at%20the%20center%2C%20neither%20vertically%20nor%20horizontally.%20their%20buttons%20are%20way%20too%20close%20to%20the%20top.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856120%22%20slang%3D%22en-US%22%3ERe%3A%20Minimize%20%2F%20Restore%20%2F%20Close%20button%20is%20on%20unnatural%20position.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856120%22%20slang%3D%22en-US%22%3E%3CP%3EHere%20is%20an%20interesting%20finding%20of%20my%20own%20that%20the%20buttons%20are%20close%20to%20File%20Explorer%20ones%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20369px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131845i28AE8F675CCA6D82%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Edge%20C%20buttons.png%22%20title%3D%22Edge%20C%20buttons.png%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EEdge%20C%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20220px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131846i13363101A7911C20%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Explorer%20buttons.png%22%20title%3D%22Explorer%20buttons.png%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EWindows%20Explorer%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPS%3A%20Yes%20I%20know%20my%20image%20subtitle%20for%20File%20Explorer%20is%20Windows%20Explorer%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856253%22%20slang%3D%22en-US%22%3ERe%3A%20Minimize%20%2F%20Restore%20%2F%20Close%20button%20is%20on%20unnatural%20position.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856253%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F409115%22%20target%3D%22_blank%22%3E%40HiSky%3C%2FA%3E%26nbsp%3B%20%26nbsp%3B%20I%20think%20that%20I%20figured%20out%20what%20is%20going%20on.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFirst%2C%20a%20refinement%20of%20the%20screenshot%20used%20in%20an%20earlier%20comment%2C%20this%20time%20showing%20horizontal%20block%20in%20which%20the%20Minimize%2FWindowed%2FClose%20buttons%20are%20located%2C%20with%20the%20bottom%20of%20the%20block%20underlined%20in%20red%20and%20the%20center%20line%20shown%20in%20blue%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131860i4312B544605CD933%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Centerline-1.jpg%22%20title%3D%22Centerline-1.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESecond%2C%20a%20screenshot%20of%20the%26nbsp%3BMinimize%2FWindowed%2FClose%20buttons%20in%20Edge%20Chromium%20shown%20in%20relationship%20to%20the%20tab%20bar%2C%20immediately%20to%20the%20left%20of%20the%20buttons%2C%20again%20showing%20the%20bottom%20of%20the%20block%20in%20red%20and%20the%20center%20line%20in%20blue%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20900px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131861iE182BD9AC4393A85%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Centerline-2.jpg%22%20title%3D%22Centerline-2.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20finally%2C%20a%20screenshot%20comparing%20Edge%20Chromium%20Dev%26nbsp%3B%3CSPAN%3EVersion%2078.0.268.3%20and%20Linux%20Chromium%20Version%2076.0.3809.100%20(Ubuntu%20Official%20Build)%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131862i79C560EF1CB903BD%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Centerline-3.jpg%22%20title%3D%22Centerline-3.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENote%20the%20difference%20between%20Edge%20Chromium%20and%20Linux%20Chromium.%26nbsp%3B%20%26nbsp%3BLinux%20Chromium%20uses%20two%20horizontal%20blocks%2C%20one%20for%20the%26nbsp%3BMinimize%2FWindowed%2FClose%20buttons%20and%20another%20for%20the%20tabs.%26nbsp%3B%20Edge%20Chromium%20(and%20also%2C%20I%20believe%20based%20on%20your%20screenshots%2C%20Google%20Chrome)%20for%20Windows%20compresses%20the%20two%20blocks%20into%20one%20in%20order%20to%20conform%20to%20Windows%2010%20design%20protocols%2C%20splitting%20the%20block%20between%20the%20two%20functions%2C%20right%20and%20left.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20whatever%20reason%20(probably%20inattentive%20coding)%2C%20the%26nbsp%3BMinimize%2FWindowed%2FClose%20buttons%20do%20not%20center%20vertically%20in%20the%20portion%20of%20the%20horizontal%20block%20assigned%20to%20them%20in%20either%20Google%20Chrome%20or%20Edge%20Chromium.%26nbsp%3B%26nbsp%3BThe%20issue%20also%20appears%20in%20other%20Chromium-based%20Windows%20browsers%20(e.g.%20Brave)%20that%20compress%20the%20tab%20block%20and%20the%26nbsp%3BMinimize%2FWindowed%2FClose%20buttons%20into%20a%20single%20horizontal%20block.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20seems%20to%20me%20that%20Microsoft%20should%20treat%20this%20as%20a%20bug%20and%20fix%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856266%22%20slang%3D%22en-US%22%3ERe%3A%20Minimize%20%2F%20Restore%20%2F%20Close%20button%20is%20on%20unnatural%20position.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856266%22%20slang%3D%22en-US%22%3E%3CP%3EI%20think%20I%20see%20what%20you're%20saying.%20Those%20three%20buttons%20on%20the%20top%20right%20side%20of%20Edge%20should%20be%20a%20drop%20lower%20or%20centered%20to%20scale%20in%20the%20middle%20between%20the%20top%20and%20bottom%20of%20the%20bar.%20I%20compared%20it%20side%20by%20side%20vs%20Chromium%20and%20against%20my%20Windows%2010%20task%20bar%20(I%20keep%20my%20task%20bar%20on%20top%20of%20the%20screen%20due%20to%20running%20Open%20Shell%2FClassic%20Shell)%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdge%20Canary%20vs%20Chromium%20%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131864i7A53538E644C4237%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.JPG%22%20title%3D%22Capture.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EEdge%20Against%20Task%20bar%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131865i573EC55D27BE0636%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222.JPG%22%20title%3D%222.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EChromium%20Against%20Task%20bar%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131866i4DF3E443E6655C9C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%223.JPG%22%20title%3D%223.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856284%22%20slang%3D%22en-US%22%3ERe%3A%20Minimize%20%2F%20Restore%20%2F%20Close%20button%20is%20on%20unnatural%20position.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856284%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F409115%22%20target%3D%22_blank%22%3E%40HiSky%3C%2FA%3E%26nbsp%3B%20%26nbsp%3BFor%20what%20it%20is%20worth%2C%20I%20found%20one%20version%20of%20Chromium%20for%20Linux%20(a%20build%20for%20Fedora)%20that%20seems%20to%20have%20worked%20out%20a%20way%20to%20get%20the%20vertical%20alignment%20correct%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20718px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131870i1F4304730962C529%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Centerline-5.jpg%22%20title%3D%22Centerline-5.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELet's%20hope%20that%20Microsoft%20will%20do%20the%20same%20in%20Edge%20Chromium.%26nbsp%3B%20The%20misalignment%20is%20a%20rookie%20design%2Fcoding%20mistake%2C%20and%20I'm%20surprised%20that%20it%20hasn't%20already%20been%20corrected%20somewhere%20along%20the%20line%20by%20The%20Chromium%20Project%20or%20Google.%26nbsp%3B%20%26nbsp%3BGoogle%20Chrome%20moved%20from%20two%20blocks%20to%20a%20single%20split%20block%20in%202015%20or%202016%20at%20the%20latest%2C%20based%20on%20screenshots%20I've%20found%20of%20Chrome%20in%20various%20iterations.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856286%22%20slang%3D%22en-US%22%3ERe%3A%20Minimize%20%2F%20Restore%20%2F%20Close%20button%20is%20on%20unnatural%20position.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856286%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318339%22%20target%3D%22_blank%22%3E%40tomscharbach%3C%2FA%3E%26nbsp%3BFedora%20project...%20I%20forgot%20about%20that.%20I%20run%20mine%20from%20the%20Chromium%20site%20with%20a%20third%20party%20auto%20updated%20tied%20into%20a%20task%20scheduler%20to%20update%20three%20or%20four%20times%20a%20day.%20I'll%20have%20to%20try%20out%20the%20other%20modified%20built%20of%20Chromium%20too.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fchromium.woolyss.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fchromium.woolyss.com%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECome%20to%20think%20of%20it%2C%20I%20think%20I'll%20go%20into%20Windows%20Sandbox%20and%20see%20how%20the%20icons%20look%20in%20Opera%20which%20is%20also%20built%20off%20of%20Chromium.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20already%20did%20Firefox%20so%20that%20base%20is%20covered.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856294%22%20slang%3D%22en-US%22%3ERe%3A%20Minimize%20%2F%20Restore%20%2F%20Close%20button%20is%20on%20unnatural%20position.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856294%22%20slang%3D%22en-US%22%3E%3CP%3EOpera'%20is%20centered%20(although%20their%20three%20icons%20are%20larger%20though)%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131871i7F9020486FCF189F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.JPG%22%20title%3D%22Capture.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856361%22%20slang%3D%22en-US%22%3ERe%3A%20Minimize%20%2F%20Restore%20%2F%20Close%20button%20is%20on%20unnatural%20position.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856361%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F373791%22%20target%3D%22_blank%22%3E%40ItalianAce%3C%2FA%3E%26nbsp%3B%20%26nbsp%3BThe%20current%20stable%20build%20of%20Chromium%20for%20Windows%20is%20offset%2C%20but%20only%20slightly%20so%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20888px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131878i88F06005CA6F44E6%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Centerline-6.jpg%22%20title%3D%22Centerline-6.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20offset%20is%20much%20less%20than%20the%20offset%20in%20Edge%20Chromium%2C%20though%2C%20which%20makes%20me%20wonder.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOh%20well%2C%20enough%20time%20wasted%20in%20nerd%20heaven%20for%20one%20day.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856412%22%20slang%3D%22en-US%22%3ERe%3A%20Minimize%20%2F%20Restore%20%2F%20Close%20button%20is%20on%20unnatural%20position.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856412%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318339%22%20target%3D%22_blank%22%3E%40tomscharbach%3C%2FA%3E%26nbsp%3BYeah%20the%20offset%20in%20Chromium%20isn't%20that%20bad%2C%20almost%20not%20noticeable.%20My%20above%20picture%20was%20from%20Chromium%20v.%26nbsp%3B%3CSPAN%3E79.0.3914.0%20(Build%26nbsp%3B696689).%20Edge%20just%20needs%20a%20minor%20adjustment%20of%20centering.%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20don't%20know%20how%20accurate%20this%20is%2C%20but%20when%20I%20run%20Edge%20Canary%20(78.0.276.0)%20through%20the%20whatversion.net%2Fchrome%20site%20and%20the%20other%20Chromium%20site%20I%20listed%20about%20it%20comes%26nbsp%3Bup%20as%20actually%20being%2078.0.3904.0.%20Which%20puts%20Edge%20Canary%20on%20the%20level%20of%20Chrome%20Dev%20in%20version%20comparison.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131884iF21C83B479CE9436%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.JPG%22%20title%3D%22Capture.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.whatversion.net%2Fchrome%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.whatversion.net%2Fchrome%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fomahaproxy.appspot.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fomahaproxy.appspot.com%2F%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856863%22%20slang%3D%22en-US%22%3ERe%3A%20Minimize%20%2F%20Restore%20%2F%20Close%20button%20is%20on%20unnatural%20position.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856863%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F373791%22%20target%3D%22_blank%22%3E%40ItalianAce%3C%2FA%3E%26nbsp%3B%20%26nbsp%3BWe%20can%20see%20how%20this%20issue%20developed%20by%20looking%20at%20Chromium%20screenshots%20over%20the%20years.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGeneralizing%20the%20design%20iterations%20into%20three%20rough%20periods%20of%20Chromium%20development%2C%20I%20found%20this%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20869px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F131932i24F876F7F2B4EDEA%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Centerline-7.jpg%22%20title%3D%22Centerline-7.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20looks%20like%20the%20tabs%20are%20located%20in%20a%20container%20within%20a%20header%20container%20(or%20perhaps%20layers%20--%20I%20haven't%20looked%20at%20the%20source%20code)%2C%20with%20the%20height%20of%20the%20header%20container%2Flayer%20and%20the%20offset%20of%20the%20Minimize%2FWindowed%2FClose%20buttons%20from%20the%20top%20of%20the%20header%20container%2Flayer%20changing%20over%20time.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20current%20iteration%20of%20Edge%20Chromium%20seems%20to%20have%20eliminated%20the%20margin%20between%20the%20tab%20container%2Flayer%20and%20the%20header%20container%2Flayer%20altogether%20but%20not%20adjusted%20the%20offset.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20that%20you%20are%20right%20about%20what%20needs%20to%20be%20done%20--%20a%20minor%20adjustment%20in%20offset.%26nbsp%3B%20It%20should%20be%20simple%20enough%20(again%2C%20I%20haven't%20looked%20at%20the%20source%20code%20so%20it%20might%20be%20more%20complicated%20than%20it%20seems)%20so%20I%20hope%20that%20Microsoft%20will%20attend%20to%20making%20the%20change%20before%20release%2C%20as%20some%20other%20Chromium%20builds%20have%20done.%26nbsp%3B%20It%20looks%20amateurish%20as%20it%20now%20is.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856897%22%20slang%3D%22en-US%22%3ERe%3A%20Minimize%20%2F%20Restore%20%2F%20Close%20button%20is%20on%20unnatural%20position.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856897%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318339%22%20target%3D%22_blank%22%3E%40tomscharbach%3C%2FA%3E%26nbsp%3BAgreed.%20Hopefully%20they'll%20fix%20it.%20It's%20not%20the%20end%20of%20the%20world%20if%20they%20don't%2C%20but%20at%20the%20same%20time%20it'll%20look%20better%20and%20natural%20(professional)%20if%20they%20correct%20the%20issue.%20Good%20points%20about%20the%20Chromium%20comparisons%20going%20back%20to%20the%20Windows%20XP%20days.%3C%2FP%3E%3C%2FLINGO-BODY%3E
HiSky
New Contributor

sd.pngThis is Edge Insider's position.

 

gf.pngThis is Chrome's position.

 

Edge Insider's position is unnaturally climbed up.

12 Replies

@HiSky  Good catch.  It is subtle, but the buttons are not centered vertically in the allotted horizontal bar in Edge Chromium.  In addition to the comparison to Chrome, these are the comparisons to Edge (Classic) and Firefox:

 

Min-Win-Close Buttons.jpg

 

I don't know it the difference is intentional, but it seems to me that vertical centering would be preferable to the offset.

@HiSky 

 

Edge insider Canary

Annotation 2019-09-15 171953.png

 

Google Chrome CanaryAnnotation 2019-09-15 172140.png

 

 

 

In Edge, the buttons look like they need to be moved a little downwards but that's only when you compare it to the Google Chrome.

neither of the browsers have their buttons at the center, neither vertically nor horizontally. their buttons are way too close to the top. 

Here is an interesting finding of my own that the buttons are close to File Explorer ones

 

Edge C buttons.pngEdge C

 

Explorer buttons.pngWindows Explorer

 

PS: Yes I know my image subtitle for File Explorer is Windows Explorer

@HiSky    I think that I figured out what is going on.

 

First, a refinement of the screenshot used in an earlier comment, this time showing horizontal block in which the Minimize/Windowed/Close buttons are located, with the bottom of the block underlined in red and the center line shown in blue:

 

Centerline-1.jpg

 

Second, a screenshot of the Minimize/Windowed/Close buttons in Edge Chromium shown in relationship to the tab bar, immediately to the left of the buttons, again showing the bottom of the block in red and the center line in blue:

 

Centerline-2.jpg

 

And finally, a screenshot comparing Edge Chromium Dev Version 78.0.268.3 and Linux Chromium Version 76.0.3809.100 (Ubuntu Official Build):

 

Centerline-3.jpg

 

Note the difference between Edge Chromium and Linux Chromium.   Linux Chromium uses two horizontal blocks, one for the Minimize/Windowed/Close buttons and another for the tabs.  Edge Chromium (and also, I believe based on your screenshots, Google Chrome) for Windows compresses the two blocks into one in order to conform to Windows 10 design protocols, splitting the block between the two functions, right and left. 

 

For whatever reason (probably inattentive coding), the Minimize/Windowed/Close buttons do not center vertically in the portion of the horizontal block assigned to them in either Google Chrome or Edge Chromium.  The issue also appears in other Chromium-based Windows browsers (e.g. Brave) that compress the tab block and the Minimize/Windowed/Close buttons into a single horizontal block.

 

It seems to me that Microsoft should treat this as a bug and fix it.

 

I think I see what you're saying. Those three buttons on the top right side of Edge should be a drop lower or centered to scale in the middle between the top and bottom of the bar. I compared it side by side vs Chromium and against my Windows 10 task bar (I keep my task bar on top of the screen due to running Open Shell/Classic Shell):

 

Edge Canary vs Chromium :

Capture.JPG

 

Edge Against Task bar:

2.JPG

 

Chromium Against Task bar:

3.JPG

 

 

 

 

 

 

 

@HiSky   For what it is worth, I found one version of Chromium for Linux (a build for Fedora) that seems to have worked out a way to get the vertical alignment correct:

 

Centerline-5.jpg

 

Let's hope that Microsoft will do the same in Edge Chromium.  The misalignment is a rookie design/coding mistake, and I'm surprised that it hasn't already been corrected somewhere along the line by The Chromium Project or Google.   Google Chrome moved from two blocks to a single split block in 2015 or 2016 at the latest, based on screenshots I've found of Chrome in various iterations.

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

 

Capture.JPG

 

@ItalianAce   The current stable build of Chromium for Windows is offset, but only slightly so:

 

Centerline-6.jpg

 

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.  

 

@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.

 

Capture.JPG

 

https://www.whatversion.net/chrome/

https://omahaproxy.appspot.com/

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

 

Centerline-7.jpg

 

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.

@tomscharbach Agreed. Hopefully they'll fix it. It's not the end of the world if they don't, but at the same time it'll look better and natural (professional) if they correct the issue. Good points about the Chromium comparisons going back to the Windows XP days.