Closed Bug 1869927 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 43656 - Fix automatic beacon data not overwriting old beacon data.

Categories

(Testing :: web-platform-tests, task, P4)

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox122 fixed)

Status:
RESOLVED FIXED
Milestone:
122 Branch
Tracking Flags:
Tracking Status
firefox122 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 43656 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/43656
Details from upstream follow.

Liam Brady <lbrady@google.com> wrote:

Fix automatic beacon data not overwriting old beacon data.

Automatic beacon data should be allowed to overwrite existing data. At
the moment, that does not happen. This CL fixes that behavior to match
what's expected in both the explainer and the spec.

Bug: 1511352
Change-Id: I23dd768b0105d139e3f369ed3c45d57d3c913b0f

Reviewed-on: https://chromium-review.googlesource.com/5120549
WPT-Export-Revision: 2cbfc685fb9ab0efb924eac04c33abff5eed79b2

CI Results

Ran 9 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 1 subtests

Status Summary

Firefox

OK : 1
FAIL: 1

Chrome

OK : 1
FAIL: 1

Safari

OK : 1
FAIL: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0ff2c0824883 [wpt PR 43656] - Fix automatic beacon data not overwriting old beacon data., a=testonly

https://hg.mozilla.org/mozilla-central/rev/0ff2c0824883

Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox122: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
You need to log in before you can comment on or make changes to this bug.