Resize sometimes does not happen immediately - getting the size after resize returns the old size.

Fixed Issue #15444270

Details

Created
Jan 12, 2018
Privacy
This issue is public.
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

The DRT ‘plugin_markup.flash_iframe_redirect_http’ (or other imageverification DRTs) sometimes fail due to a small delay in resize via webdriver.

Added a workaround in Bug 14391179 to make the DRT setup wait for resize to complete before proceeding.

Repro Steps:

  1. Remove the workaround fix from bug 14391179.
  2. Run the DRT 'plugin_markup.flash_iframe_redirect_http with a repeatcount of 100 or 200.
  3. The DRT fails a couple of times because of resizing problems.

Root-cause for DRT failure:
The Webdriver test setup PerformSanityNavTest() resizes Edge to 800 x 600. The ImageVerification test setup then attempts resizes Edge to 640 x 480 before running the tests and taking a screenshot.

In the failure case, ImageVerification code checks the current size and it returns 640 x 480 (which was the previous size before PerformSanityNavTest() resized it to 800 x 600). So, it doesn’t resize it again. However, the 800 x 600 resize happens some time after this which causes the screenshot that is taken to be of a different size than the reference image. This causes the test to fail.

The expectation is that the resize should have completed by the time get size is called in ImageVerification test setup.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Status to “Confirmed”

      Changed Assigned To to “edgedevtoolstri”

      Changed Assigned To from “edgedevtoolstri” to “Clay M.”

      Changed Assigned To from “Clay M.” to “Navin A.”

      Changed Status from “Confirmed”

      Changed Assigned To from “Navin A.” to “Long L.”

      Changed Status

      Changed Status to “Confirmed”

      Changed Status from “Confirmed”

      Changed Assigned To from “Long L.” to “Clay M.”

    • I’m facing a similar experience to the described in a regression fashion; we’ve tested on Edge 15, 16, and 17 and are only getting this issue on 17.

    • Microsoft Edge Team

      Changed Assigned To from “Clay M.” to “Long L.”

      Changed Assigned To from “Long L.” to “Clay M.”

      Changed Assigned To from “Clay M.” to “Mustapha J.”

      Changed Assigned To from “Mustapha J.” to “Navin A.”

      Changed Status to “Fixed”

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

    Sign in