2026147 - High frequency /content-security-policy/inheritance/history.sub.html | History navigation: "about:blank" document is navigated back from history same-origin. - step_wait_func: Wait for the popup to navigate. Timed out waiting | single tracking bug

Status: RESOLVED FIXED

(Core :: DOM: Security, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: rperta [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=555480862&repo=autoland&task=UGJrNSYbQlaw37-QpzAltQ.0
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/UGJrNSYbQlaw37-QpzAltQ/runs/0/artifacts/public/logs/live_backing.log

---

[task 2026-03-25T09:52:19.946+00:00] 09:52:19     INFO - TEST-PASS | /content-security-policy/inheritance/history-iframe.sub.html | History navigation in iframe: data URL document is navigated back from history same-origin.
[task 2026-03-25T09:52:19.946+00:00] 09:52:19     INFO - TEST-PASS | /content-security-policy/inheritance/history-iframe.sub.html | History navigation in iframe: data URL document is navigated back from history cross-origin.
[task 2026-03-25T09:52:19.946+00:00] 09:52:19     INFO - TEST-PASS | /content-security-policy/inheritance/history-iframe.sub.html | History navigation in iframe: srcdoc iframe is navigated back from history same-origin.
[task 2026-03-25T09:52:19.946+00:00] 09:52:19     INFO - TEST-PASS | /content-security-policy/inheritance/history-iframe.sub.html | History navigation in iframe: srcdoc iframe is navigated back from history cross-origin.
[task 2026-03-25T09:52:19.946+00:00] 09:52:19     INFO - TEST-UNEXPECTED-FAIL | /content-security-policy/inheritance/history.sub.html | History navigation: "about:blank" document is navigated back from history same-origin. - step_wait_func: Wait for the popup to navigate. Timed out waiting on condition
[task 2026-03-25T09:52:20.048+00:00] 09:52:20     INFO - TEST-OK | /content-security-policy/inheritance/history.sub.html | took 12500ms
[task 2026-03-25T09:52:20.719+00:00] 09:52:20     INFO - Closing logging queue
[task 2026-03-25T09:52:20.719+00:00] 09:52:20     INFO - queue closed
[task 2026-03-25T09:52:20.728+00:00] 09:52:20     INFO - STDOUT: cleanup aborted: args: /builds/worker/fetches/android-sdk-linux/platform-tools/adb wait-for-device remount, exitcode: 1, stdout: Device must be bootloader unlocked
[task 2026-03-25T09:52:20.733+00:00] 09:52:20     INFO - Setting up ssl
[task 2026-03-25T09:52:20.754+00:00] 09:52:20     INFO - certutil | b''
[task 2026-03-25T09:52:20.774+00:00] 09:52:20     INFO - certutil | b''
[task 2026-03-25T09:52:20.787+00:00] 09:52:20     INFO - certutil | b'\nCertificate Nickname                                         Trust Attributes\n                                                             SSL,S/MIME,JAR/XPI\n\nweb-platform-tests                                           CT,, \n'
[task 2026-03-25T09:52:21.815+00:00] 09:52:21     INFO - adb Granting important runtime permissions to org.mozilla.geckoview.test_runner
[task 2026-03-25T09:52:21.957+00:00] 09:52:21     INFO - adb launch_application: am start -W -n org.mozilla.geckoview.test_runner/org.mozilla.geckoview.test_runner.TestRunnerActivity -a android.intent.action.MAIN --es env0 MOZ_CRASHREPORTER=1 --es env1 MOZ_CRASHREPORTER_NO_REPORT=1 --es env2 MOZ_CRASHREPORTER_SHUTDOWN=1 --es env3 MOZ_HIDE_RESULTS_TABLE=1 --es env4 MOZ_IN_AUTOMATION=1 --es env5 MOZ_LOG=signaling:3,mtransport:4,DataChannel:3,jsep:4 --es env6 R_LOG_LEVEL=6 --es env7 R_LOG_DESTINATION=stderr --es env8 R_LOG_VERBOSE=1 --es env9 MOZ_PROCESS_LOG=/tmp/tmpzv328ob9pidlog --es env10 MINIDUMP_SAVE_PATH=/builds/worker/workspace/build/blobber_upload_dir --es env11 MOZ_DISABLE_NONLOCAL_CONNECTIONS=1 --es arg0 -no-remote --es arg1 -profile --es arg2 /data/local/tmp/test_root/profile --es arg3 --marionette --es arg4 --remote-allow-system-access --es arg5 about:blank
[task 2026-03-25T09:52:24.802+00:00] 09:52:24     INFO - Starting runner
[task 2026-03-25T09:52:29.871+00:00] 09:52:29     INFO - TEST-START | /content-security-policy/inheritance/iframe-all-local-schemes.sub.html
[task 2026-03-25T09:52:29.919+00:00] 09:52:29     INFO - Setting pref layout.disable-pixel-alignment to true
[task 2026-03-25T09:52:29.975+00:00] 09:52:29     INFO - Setting pref layout.css.anchor-positioning.enabled to true
[task 2026-03-25T09:52:30.016+00:00] 09:52:30     INFO - Setting pref dom.security.trusted_types.enabled to true
[task 2026-03-25T09:52:32.046+00:00] 09:52:32     INFO - TEST-OK | /content-security-policy/inheritance/iframe-all-local-schemes.sub.html | took 2178ms
[task 2026-03-25T09:52:32.047+00:00] 09:52:32     INFO - TEST-START | /content-security-policy/inheritance/iframe-srcdoc-history-inheritance.html

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

:kinetik, since you are the author of the regressor, bug 2026000, could you take a look?

For more information, please visit BugBot documentation.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 2026000

Comment 3

[Matthew Gregan [:kinetik]]

I'm confused, I think the regressing bug is misattributed. Bug 2026000 hit autoland at 25 Mar 2026 13:56:31 +0000. The failing test is in an autoland job from 25 Mar 2026 08:58:24 +0000, 5 hours earlier. Bug 2026000 is an Android audio backend change, but the failing test doesn't use audio AFAICT.

We have had lots of unrelated-to-audio tests failing on the Android emulator runners due to audio bugs, however. Bug 2025563 hit autoland at 24 Mar 2026 08:21:50 +0000, that was intended to fix those random timeouts, but may have caused some to shift to other bugs - OTOH if this test timeout is high frequency, I'd expect it to show up sooner and be more clearly linked to that bug landed. I don't have any evidence that this test timeout is related to bug 2025563 or audio yet, but I'll check.

Comment 4

[Matthew Gregan [:kinetik]]

I don't think this timeout is audio related at all. In the linked failing job's logcat-emulator-5554.log, we can see:

09:49:00.970 - emulator boot
09:49:25.352 - Android audio init completes
09:51:47.131 - GeckoView test runner (7528) starts
09:52:07.473 - history.sub.html test starts in 7528
09:52:19.525 - Process 7528 killed, test timeout reported
09:59:16.884 - GeckoView test runner (28384) starts
10:00:17.235 - media-source tests start in 28384
10:00:20.539 - First AAudioStream (s#1) since boot created

So Gecko hasn't done anything audio related until after the history.sub.html test has timed out.

Comment 5

[Intermittent Failures Robot]

17 failures were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 14
• mozilla-central: 3

Table

	nofis
android-x86_64/debug	16
android-x86_64/opt	1

For more details, see:

https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=2026147&startday=2026-03-23&endday=2026-03-29&tree=all

Comment 6

[Intermittent Failures Robot]

24 failures were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-central: 2
• autoland: 22

Table

	nofis	nofis-s	standalone
android-x86_64/debug	16	3
android-x86_64/opt	4
linux2404-x86_64/opt			1

For more details, see:

https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=2026147&startday=2026-03-30&endday=2026-04-05&tree=all

Comment 7

[Intermittent Failures Robot]

18 failures were associated with this bug yesterday.

Repository breakdown:

• autoland: 18

Table

	nofis	nofis-s
android-x86_64/debug	11	2
android-x86_64/opt	2	3

For more details, see:

https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=2026147&startday=2026-04-07&endday=2026-04-07&tree=all

Comment 8

[Intermittent Failures Robot]

59 failures were associated with this bug in the last 7 days.

This failure happened more than 30 times this week! Resolving this bug is a high priority.

Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled.

Repository breakdown:

• autoland: 56
• mozilla-central: 3

Table

	nofis	nofis-s
android-x86_64/debug	45	8
android-x86_64/opt	5	1

For more details, see:

https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=2026147&startday=2026-04-08&endday=2026-04-14&tree=all

Comment 9

[Intermittent Failures Robot]

55 failures were associated with this bug in the last 7 days.

This failure happened more than 30 times this week! Resolving this bug is a high priority.

Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled.

Repository breakdown:

• autoland: 48
• mozilla-central: 3
• try: 4

Table

	nofis	nofis-s
android-x86_64/debug	48	6
android-x86_64/opt	1

For more details, see:

https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=2026147&startday=2026-04-13&endday=2026-04-19&tree=all

Comment 10

[Intermittent Failures Robot]

44 failures were associated with this bug in the last 7 days.

This failure happened more than 30 times this week! Resolving this bug is a high priority.

Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled.

Repository breakdown:

• autoland: 37
• mozilla-central: 6
• try: 1

Table

	nofis	nofis-s
android-x86_64/debug	34	8
android-x86_64/opt	2

For more details, see:

https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=2026147&startday=2026-04-20&endday=2026-04-26&tree=all

Comment 11

[Matthew Gregan [:kinetik]]

Bug 1706538 seems a more likely candidate. Vincent, do you mind taking a look please?

Comment 12

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1706538

Comment 13

[Intermittent Failures Robot]

15 failures were associated with this bug yesterday.

Repository breakdown:

• autoland: 13
• mozilla-central: 2

Table

	nofis	nofis-s
android-x86_64/debug	13	2

For more details, see:

https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=2026147&startday=2026-04-28&endday=2026-04-28&tree=all

Comment 14

[Vincent Hilla [:vhilla]]

Oh yes, they were annotated as intermittent and I hoped that that patch or bug 543435 fixed this. I'll look into if only this one subtest is intermittent or all intermittent annotations should be restored. Thanks!

Comment 15

[Vincent Hilla [:vhilla]]

The two tests should've been fixed by my change, but are still intermittent. I think it's because of this code or similar. Some observations:

After navigating from postmessage-opener.html to about:blank, popup.history.length is sometimes 1. This indicates we did a replace load because postmessage-opener.html didn't complete loading when it sent it's message and was navigated away. This seems fixed by sending the message on load instead of during parsing. Doing the navigation to about:blank during load would still break, but waiting for the message should be async enough.

When we then navigate from about:blank to message-opener-and-navigate-back.html, it's more difficult to check history.length due to being xorigin. But I suppose the same happens, even more likely because we just poll for popup.location.href without ensuring about:blank has finished loading. I guess we can't reliably catch the load event for about:blank in a popup. I at least confirmed on try that when we fail, history.back() causes us to go too far back to postmessage-opener.html. Perhaps waiting for readyState next to location is sufficient.

For history-iframe.sub.html, it should be fine to just wait for load instead of polling location Edit: in theory yes, but waiting for complete is simpler. If I just wait for the about:blank load event, it's still flaky. I suppose it sometimes gets the load event for postmessage-top.html because the message might arrive earlier.

Comment 16

[Vincent Hilla [:vhilla]]

Attachment: Bug 2026147 - Avoid flakiness in history{-iframe}.sub.html. r=#dom-core

Comment 17

[Intermittent Failures Robot]

49 failures were associated with this bug in the last 7 days.

This failure happened more than 30 times this week! Resolving this bug is a high priority.

Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled.

Repository breakdown:

• autoland: 44
• mozilla-central: 5

Table

	nofis	nofis-s	s
android-x86_64/debug	40	8
macosx1500-aarch64/debug			1

For more details, see:

https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=2026147&startday=2026-04-27&endday=2026-05-03&tree=all

Comment 18

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/329705a5c23d
https://hg.mozilla.org/integration/autoland/rev/91d0458eb329
Avoid flakiness in history{-iframe}.sub.html. r=dom-core,smaug

Comment 19

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/59667 for changes under testing/web-platform/tests

Comment 20

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/91d0458eb329

Comment 21

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Upstream PR merged by moz-wptsync-bot

Comment 22

[BugBot [:suhaib / :marco/ :calixte]]

The patch landed in nightly and beta is affected.
:vhilla, is this bug important enough to require an uplift?

• If yes, please nominate the patch for beta approval.
  • See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
• If no, please set status-firefox151 to wontfix.

For more information, please visit BugBot documentation.

Comment 23

[Vincent Hilla [:vhilla]]

It's just a test fix, so not really important. Unsure if this warrants an uplift given the zero risk to avoid intermittents on beta / release branch testing. I tend towards no, but happy to file the request if needed.

Comment 24

[Intermittent Failures Robot]

10 failures were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 9
• mozilla-central: 1

Table

	nofis
android-x86_64/debug	10

For more details, see:

https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=2026147&startday=2026-05-04&endday=2026-05-10&tree=all