Microsoft Edge still not honoring width and height correctly - even in 10586

Fixed, not yet flighted Issue #5633598


Nov 30, 2015
This issue is public.
Reported by 7 people

Sign in to watch or report this issue.

Steps to reproduce


Repro Steps:

Set parent window to anything but full-screen. The opened window will have same size as parent window
However, if I maximize parent window then the opened window will honor width and height.

Expected Results:

That will honor width and height no matter if the parent window is maximized / full screen.

Actual Results:

Dev Channel specific:



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Kamen M.”

      Changed Assigned To to “Christian F.”

      Changed Assigned To to “Travis L.”

      Changed Assigned To to “Mara P.”

      Changed Assigned To from “Mara P.” to “Tom B.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Tom B.” to “Adam B.”

      Changed Assigned To from “Adam B.” to “IE S.”

      Changed Status from “Confirmed” to “Fixed, not yet flighted”

    • If this is a duplicate, can you please mention the issue that this a duplicate of ?
      I’m facing the exact same issue in the same build.

    • Microsoft marked both as duplicates: but you can find them both here:

      Original here: - many people still have issues with this problem. Microsoft, are you monitoring this??

    • MSFT - Can you please reopen this ? The original is marked as closed, but the problem still persists.

    • Any updates to this Microsoft?

    • I’m seeing this issue as well. What is the official word from Microsoft on this issue.

    • On the website I was building, I was having the same issue when trying to take user to a complete URL (eg, “”). The issue was not there when the URL specified was relative (eg, “…/Files/Default.aspx”). I designed the approach where instead of taking user directly to the fully qualified URL, I am now talking user to an internal page having desired dimensions (using, and then sending user to the desired destination (external website link) using Response.Redirect. This is working out gracefully without any issues.

      It almost seems as if Edge was taking a fully qualified URL as a request to open a new browser window as done using the Edge menu.

      Sharing this workaround, if there is still a need for this solution.

    • It has been marked as “Fixed, not yet flighted” since Mar 22, 2016. I works now for me (and has been doing so for a long time. So maybe it is time to change the status to "Released"?

    You need to sign in to your Microsoft account to add a comment.

    Sign in