ProgressEvent() constructor options loaded + total accept double in Chrome 136 + Firefox 138

[bsmth]

Summary

This allows specifications to use ProgressEvents while not necessarily giving away the exact number of bytes, for example by using numbers between 0 and 1

Test results and supporting details

• Chromium: https://issues.chromium.org/issues/381969448
• Gecko: https://bugzilla.mozilla.org/show_bug.cgi?id=1943649
• WebKit: https://bugs.webkit.org/show_bug.cgi?id=288688

WPT: https://wpt.fyi/results/xhr/progressevent-constructor.html?label=master&label=stable&product=chrome&product=firefox&product=safari&product=edge&aligned

Related issues

• Content PR: chore: Change ints to 'number' for ProgressEvent properties content#39574
• Original tracker: Update ProgressEvent documentation to show it allows doubles mdn#641

[github-actions]

Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

[bsmth]

I'm open to suggestions whether this should be one entry under the constructor - I'm thinking this might make more sense as:

"description": "`loaded` and `total` accept decimal values",

[caugner]

The data looks good to me, but:

1. The term "decimals" could be misleading here (cf. decimal list type). Let's use double as mentioned in the spec.
2. Since loaded and total are readonly, I would say this is more a feature of the constructor. Let's add one behavioral subfeature there instead: api.ProgressEvent.ProgressEvent.loaded_total_options_accept_double.

[bsmth]

Great, tnx. Agree on both points.

[bsmth]

Thank you!