Home

Two adjacent Edge instances end up on top of one another after Relaunch

%3CLINGO-SUB%20id%3D%22lingo-sub-506371%22%20slang%3D%22en-US%22%3ETwo%20adjacent%20Edge%20instances%20end%20up%20on%20top%20of%20one%20another%20after%20Relaunch%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-506371%22%20slang%3D%22en-US%22%3E%3CP%3E1-%20Launch%20two%20instances%20of%20Edge%20Canary%3C%2FP%3E%3CP%3E2-%20Place%20them%20side%20by%20side%20using%20Windows'%20Win%20key%20%2B%20arrows%3C%2FP%3E%3CP%3E3-%20Make%20a%20change%20to%20a%20flag%20in%20edge%3A%2F%2Fflags%3C%2FP%3E%3CP%3E4-%20Click%20on%20Relaunch%20Now%3C%2FP%3E%3CP%3E5-%20Expected%20behaviour%3A%20both%20instances%20come%20back%20the%20way%20they%20were%20(side%20by%20side)%3C%2FP%3E%3CP%3E6-%20Result%3A%20sometimes%20the%20instances%20come%20back%20on%20top%20of%20one%20another%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-506490%22%20slang%3D%22en-US%22%3ERe%3A%20Two%20adjacent%20Edge%20instances%20end%20up%20on%20top%20of%20one%20another%20after%20Relaunch%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-506490%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F316442%22%20target%3D%22_blank%22%3E%40NicolSD%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3ENicol%2C%20it%2C%20also%2C%20does%20that%2C%20I%20find%2C%20if%20keep%20opening%20from%20the%20taskbar.%26nbsp%3B%20They%20sit%20so%20much%20on%20top%20of%20each%20other%20you%20can%20barely%20see%20the%20edge%20(no%20pun)%20of%20one%20'underneath'!%26nbsp%3B%20This%20definitly%20needs%20to%20be%20rectified%20asap.%26nbsp%3B%20Both%20issues.%3CBR%20%2F%3E%3CBR%20%2F%3ECheers%2C%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3EDrew%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20113px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F111240i1D16C88BE9C5FA58%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22thVY64FD02.jpg%22%20title%3D%22thVY64FD02.jpg%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-507590%22%20slang%3D%22en-US%22%3ERe%3A%20Two%20adjacent%20Edge%20instances%20end%20up%20on%20top%20of%20one%20another%20after%20Relaunch%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-507590%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F316442%22%20target%3D%22_blank%22%3E%40NicolSD%3C%2FA%3E%26nbsp%3B%20It%20sounds%20like%20the%20Canary%20build%20you%20are%20testing%20intermittently%20ignore%20Snap%2C%20failing%20to%20retain%20either%20Snap%20sizing%20(that%20is%2C%20relaunch%20as%20full%20screen)%20or%20Snap%20positioning%20(that%20is%2C%20retain%20half-sizing%20but%20overlay%20one%20another)%20upon%20relaunch.%26nbsp%3B%20%26nbsp%3BIf%20I%20have%20that%20right%2C%20it%20is%20probably%20an%20issue%20you%20should%20report%20to%20Microsoft%20Edge%20Support%20after%20you've%20documented%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-508030%22%20slang%3D%22en-US%22%3ERe%3A%20Two%20adjacent%20Edge%20instances%20end%20up%20on%20top%20of%20one%20another%20after%20Relaunch%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-508030%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%3BLOL%20--%20Finding%20the%20bugs%20isn't%20half%20the%20game.%20Finding%20how%20it%20happens%20is%20the%20real%20tough%20part.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-509520%22%20slang%3D%22en-US%22%3ERe%3A%20Two%20adjacent%20Edge%20instances%20end%20up%20on%20top%20of%20one%20another%20after%20Relaunch%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-509520%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20also%20been%20able%20to%20replicate%20it%20on%20my%20Win10%20Build%2018890%20Workstation%20using%20Edge%20Dev%20build%26nbsp%3B%3CSPAN%3E75.0.139.1.%20The%20Dev%20build%20has%20no%20extensions%20and%20three%20flags%20enabled%3A%20HDR%20mode%2C%20Enable%20native%20notifications%2C%20and%20Microsoft%20Edge%20theme.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-509466%22%20slang%3D%22en-US%22%3ERe%3A%20Two%20adjacent%20Edge%20instances%20end%20up%20on%20top%20of%20one%20another%20after%20Relaunch%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-509466%22%20slang%3D%22en-US%22%3E%3CP%3EOK%2C%20I%20have%20been%20able%20to%20get%20the%26nbsp%3Bbug%20to%20repeat%20on%20my%20Surface%20Pro%204.%20It%20has%20Edge%20Canary%2076.0.146.0%2C%20no%20extensions%20installed%2C%20no%20flags%20changed.%20The%20Surface%20is%20running%20Windows%2010%20Build%2018890.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1-%20Launch%20two%20instances%20of%20Edge%20Canary%3C%2FP%3E%3CP%3E2-%20Place%20them%20side%20by%20side%20using%20Win%20%2B%20arrows%3C%2FP%3E%3CP%3E3-%20Open%20Edge%3A%2F%2Fflags%3C%2FP%3E%3CP%3E4-%20Look%20for%20Microsoft%20Edge%20theme%3C%2FP%3E%3CP%3E5-%20Set%20it%20to%20Enabled%3C%2FP%3E%3CP%3E6-%20Relaunch%3C%2FP%3E%3CP%3E7-%20The%20two%20windows%20will%20reopen%20not%20quite%20where%20they%20were%20first%20placed%2C%20are%20slightly%20smaller%20and%20overlap%20a%20bit.%20Otherwise%2C%20the%20behaviour%20is%20ok.%3C%2FP%3E%3CP%3E8-%20Go%20to%20the%20Edge%3A%2F%2Fflags%20window%20and%20set%20Microsoft%20Edge%20theme%20to%20Default%3C%2FP%3E%3CP%3E9-%20Relaunch%3C%2FP%3E%3CP%3E10-%20The%20two%20windows%20will%20be%20almost%20perfectly%20on%20top%20of%20one%20another.%20One%20will%20be%20slightly%20recessed%2C%20both%20vertically%20and%20horizontally.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20I%20said%2C%20these%20steps%20are%20repeatable%20on%20my%20Surface%20Pro%204.%20I%20have%20been%20able%20to%20repeat%20the%20same%20steps%20five%20times%20and%20%3CSTRONG%3Eit%20always%20overlaps%20the%20second%20time%3C%2FSTRONG%3E%20I%20relaunch%20Edge.%20However%2C%20the%20bug%20has%20proven%20evasive%20on%20my%20workstation.%20So%20far%2C%20it%20hits%20when%20it%20wants.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-509840%22%20slang%3D%22en-US%22%3ERe%3A%20Two%20adjacent%20Edge%20instances%20end%20up%20on%20top%20of%20one%20another%20after%20Relaunch%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-509840%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F316442%22%20target%3D%22_blank%22%3E%40NicolSD%3C%2FA%3E%26nbsp%3B%20Good%20work%2C%20Nichol.%26nbsp%3B%20%26nbsp%3BWhen%20you%20report%20this%20in%20to%20Microsoft%20Edge%20Support%2C%20they%20should%20be%20able%20to%20replicate%20it%2C%20based%20on%20your%20logs%2C%20without%20much%20difficulty.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-566627%22%20slang%3D%22en-US%22%3ERe%3A%20Two%20adjacent%20Edge%20instances%20end%20up%20on%20top%20of%20one%20another%20after%20Relaunch%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-566627%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20bug%20is%20fixed%20as%20of%20build%2076.0.159.0.%20That%20bug%20was%20reported%20here%20and%20through%20Mr.%20Smiley.%20I%20did%20exchange%20with%20an%20MS%20rep%20for%20a%20while%2C%20then%20we%20waved%20goodbye%20once%20he%20felt%20he%20had%20all%20the%20information%20he%20needed.%20I%20never%20heard%20back%20from%20MS%20after%20that.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20now%20going%20to%20complain%20again%20about%20MS's%20lack%20of%20feedback.%20I%20first%20reported%20the%20problem%20at%20the%20end%20of%20April.%20Then%20I%20had%20my%20exchange%20with%20the%20rep.%20But%20ever%20since%20that%20time%2C%20I%20have%20been%20testing%20the%20same%20bug%20with%20every%20single%20build%20until%20I%20discovered%20today%20that%20it's%20finally%20fixed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20the%20only%20thing%20I%20know%20for%20sure%20is%20that%20the%20problem%20is%20fixed%20for%20me.%20Would%20others%20go%20back%20to%20the%20first%20post%20and%20try%20to%20replicate%20the%20problem%20so%20that%20we%20may%20be%20certain%20is%20truly%20has%20been%20fixed%20for%20good.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat's%20another%20one%20of%20my%20bugs%20that%20was%20fixed%20today.%20Thank%20you%2C%20MS%20for%20not%20telling%20me!%3C%2FP%3E%3C%2FLINGO-BODY%3E
NicolSD
Regular Contributor

1- Launch two instances of Edge Canary

2- Place them side by side using Windows' Win key + arrows

3- Make a change to a flag in edge://flags

4- Click on Relaunch Now

5- Expected behaviour: both instances come back the way they were (side by side)

6- Result: sometimes the instances come back on top of one another

6 Replies

@NicolSD  It sounds like the Canary build you are testing intermittently ignore Snap, failing to retain either Snap sizing (that is, relaunch as full screen) or Snap positioning (that is, retain half-sizing but overlay one another) upon relaunch.   If I have that right, it is probably an issue you should report to Microsoft Edge Support after you've documented it.

@tomscharbach LOL -- Finding the bugs isn't half the game. Finding how it happens is the real tough part.

OK, I have been able to get the bug to repeat on my Surface Pro 4. It has Edge Canary 76.0.146.0, no extensions installed, no flags changed. The Surface is running Windows 10 Build 18890.

 

1- Launch two instances of Edge Canary

2- Place them side by side using Win + arrows

3- Open Edge://flags

4- Look for Microsoft Edge theme

5- Set it to Enabled

6- Relaunch

7- The two windows will reopen not quite where they were first placed, are slightly smaller and overlap a bit. Otherwise, the behaviour is ok.

8- Go to the Edge://flags window and set Microsoft Edge theme to Default

9- Relaunch

10- The two windows will be almost perfectly on top of one another. One will be slightly recessed, both vertically and horizontally.

 

As I said, these steps are repeatable on my Surface Pro 4. I have been able to repeat the same steps five times and it always overlaps the second time I relaunch Edge. However, the bug has proven evasive on my workstation. So far, it hits when it wants.

I have also been able to replicate it on my Win10 Build 18890 Workstation using Edge Dev build 75.0.139.1. The Dev build has no extensions and three flags enabled: HDR mode, Enable native notifications, and Microsoft Edge theme.

@NicolSD  Good work, Nichol.   When you report this in to Microsoft Edge Support, they should be able to replicate it, based on your logs, without much difficulty.

The bug is fixed as of build 76.0.159.0. That bug was reported here and through Mr. Smiley. I did exchange with an MS rep for a while, then we waved goodbye once he felt he had all the information he needed. I never heard back from MS after that.

 

I am now going to complain again about MS's lack of feedback. I first reported the problem at the end of April. Then I had my exchange with the rep. But ever since that time, I have been testing the same bug with every single build until I discovered today that it's finally fixed.

 

But the only thing I know for sure is that the problem is fixed for me. Would others go back to the first post and try to replicate the problem so that we may be certain is truly has been fixed for good.

 

That's another one of my bugs that was fixed today. Thank you, MS for not telling me!