Closed
Bug 2024806
Opened 2 months ago
Closed 1 month ago
[wpt-sync] Sync PR 58573 - maps "progress-function" web feature
Categories
(Core :: CSS Parsing and Computation, task, P4)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
151 Branch
| Tracking | Status | |
|---|---|---|
| firefox151 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 58573 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/58573
Details from upstream follow.
Chris Cuellar <58723+ChrisC@users.noreply.github.com> wrote:
maps "progress-function" web feature
web feature docs: https://github.com/web-platform-dx/web-features/blob/main/features/progress-function.yml
cc @jugglinmike for review
As of 2025-12-05, the wpt-pr-bot is requesting reviews from code owners for changes to WEB_FEATURES.yml files. To learn more about the purpose of these files, check out this presentation from TPAC 2025, Annotating WPT to Surface the Status of the Platform
| Assignee | ||
Updated•2 months ago
|
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
| Assignee | ||
Updated•2 months ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
| Assignee | ||
Updated•2 months ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
| Assignee | ||
Comment 1•2 months ago
|
||
| Assignee | ||
Comment 2•2 months ago
|
||
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Pushed by wptsync@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/70c7486d7d5b
https://hg.mozilla.org/integration/autoland/rev/e6ffa3103b03
[wpt PR 58573] - maps "progress-function" web feature, a=testonly
Comment 4•1 month ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 month ago
status-firefox151:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 151 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•