When resizeTo is called on a new window immediately after window.open, it usually does not work (no resize or resizes parent)

Fixed, flighted Issue #8440534

Details

Author
Jonathan S.
Created
Aug 9, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14
Fixed in build #
15018
Reports
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

  1. Open a new window
  2. Call the window’s resizeTo method
  3. Note that parent window gets resized

The attached HTML file reproduces this issue; you may need to run the test two or three times in order to trigger the buggy behavior.

Workaround:

In the attached file, if you move the call to resizeTo into the setTimeout, the parent window will not be resized. The reproduction requires that resizeTo be called immediately after the window has been opened.

Attachments

1 attachment

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Ibrahim O.”

    Changed Assigned To to “Travis L.”

    Changed Assigned To to “Christian F.”

    Changed Status to “Confirmed”

    Changed Assigned To from “Christian F.” to “Warren S.”

    Changed Status from “Confirmed”

    Changed Assigned To from “Warren S.” to “Rose Z.”

    Changed Status to “Confirmed”

    Changed Status from “Confirmed”

    Changed Assigned To to “Kamen M.”

    Changed Assigned To from “Kamen M.” to “Rose Z.”

    Changed Status to “Confirmed”

    Changed Status from “Confirmed” to “In progress”

    Changed Title from “Resizing Popup, Resizes Parent” to “When resizeTo is called on a new window immediately after window.open, it usually does not work (no resize or resizes parent)”

    Changed Status from “In progress” to “In code review”

    Changed Status from “In code review” to “In progress”

    Changed Status from “In progress” to “Fixed, not yet flighted”

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

  • Hello,

    Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 15063 and is available in our latest Insider Preview build.

    Best Wishes,
    The MS Edge Team

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

Sign in