Using Microsoft Edge on Windows 10.

If we use middle click to close tab, the browser goes to other monitor.
Seems like a bug.

On my system at least, if you middle click on a blank area of the tab bar it will move to the next screen but if you middle click on a tab then that tab will close.
Which build of Windows 10 are you using, I ask because Microsoft have done a lot of work on the Edge browser and that could be the reason why my version of Edge behaves properly.

Edit

Yep mine does the same but it is inconsistant and seems to be more on the first tab??

Yup. The right behaviour is to close the tab only. But seems that the parent of the tab is called, so it closes the tab AND move to the next monitor.

I tried on the middle tabs....
Btw, it happened on Anniversary updates and now the latest insiders build.

I recognize this is a very old post, but I have related comments regarding this reported issue, and I'm not sure how to bring them to the attention of developers (or if I should), and it seemed commenting here might be better than starting a new thread.

While this is fixed in current versions of Edge, the new Chromium-based Edge still has this issue. When a tab is middle-clicked in order to close it, DisplayFusion behaves as though the title bar has been clicked, moving the browser window to the next monitor. Of note, the tab is still not closed, so DF is intercepting the click event, preventing it from being passed to Edge.

While this version of Edge is still in beta, it seems unlikely this is an issue that will be "fixed" on their at any point, since it's not an issue with Edge itself. On the off-chance they would consider looking into it it, I actually did submit a ticket regarding the behavior, to see if the way they were handling the click event was non-standard. As expected, the response was essentially "there's no problem."

Is this something the DF team will look into? I see no reason the team couldn't go ahead and add it to the backlog, but I realize it won't be super high-priority until Edge's official public release.

My question is: Should I report it as an issue now, or will I have to wait until the release version is published?

Thanks. After trying it, it does seem to be fixed. I do notice that middle- clicking elsewhere on the bar no longer moves the window to the next monitor, though the button is still available to do it.

To be honest, though I use that feature so little that I don't know whether this was already the case with browsers that essentially use the title bar to hold tabs, or if it is a concession that has been made as a workaround for this issue.