Closed Bug 1498282 Opened 11 months ago Closed 11 months ago

On Linux, resistfingerprinting content resize tests can get earlier resize event and get confused about final window sizing when not loading initial about:blank

Categories

(Firefox :: General, defect, P2)

defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox64 --- affected

People

(Reporter: Gijs, Assigned: Gijs)

References

(Blocks 1 open bug)

Details

Attachments

(1 obsolete file)

Spotted in https://treeherder.mozilla.org/#/jobs?repo=try&selectedJob=203135076&revision=52f0d7b35760ac92e7eb677bc99645b697a86b3b

TEST-UNEXPECTED-FAIL | browser/components/resistfingerprinting/test/browser/browser_roundedWindow_windowSetting_mid_inner.js | The screen.height has a correct rounded value - 100 == 600 -
TEST-UNEXPECTED-FAIL | browser/components/resistfingerprinting/test/browser/browser_roundedWindow_windowSetting_mid_inner.js | The window.innerHeight has a correct rounded value - 100 == 600 -
Return code: 1

Because we initially open the window at 100x100 and then set window.inner/outerWidth/Height with a content task, it's possible the resize handler triggers for the first size of the window (on Linux, where window sizing + focusing is async), and that causes the test to fail.

Similar to the changes made in bug 1489700, we can just wait for the correct resize event and that'll make the test pass.
Priority: -- → P2
Not seeing issues here anymore atm, can reopen if this reappears.
Status: ASSIGNED → RESOLVED
Closed: 11 months ago
Resolution: --- → WORKSFORME
Attachment #9016352 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.