chore: Change ints to 'number' for ProgressEvent properties

[bsmth]

Description

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 … with 6 decimal digits

The docs are explicit about ints here, and changes have landed allowing doubles:

https://xhr.spec.whatwg.org/#dom-progresseventinit-loaded

• Chromium Intent to Ship
• WebKit bug
• Gecko bug

Related issues and pull requests

Fixes mdn/mdn#641

• BCD: ProgressEvent() constructor options loaded + total accept double in Chrome 136 + Firefox 138 browser-compat-data#26956

[bsmth]

CC @domenic

[github-actions]

Preview URLs

• /en-US/docs/Web/API/ProgressEvent/ProgressEvent
• /en-US/docs/Web/API/ProgressEvent/loaded
• /en-US/docs/Web/API/ProgressEvent/total
• /en-US/docs/Web/API/ProgressEvent

(comment last updated: 2025-06-02 16:20:46)

[Josh-Cena]

This would need BCD too I reckon, +1 for content, but not sure if it fixes the issue completely.

Also as a reader I would be curious to know what a fraction of a byte even means.

[bsmth]

Also as a reader I would be curious to know what a fraction of a byte even means.

Yeah that's a good point, motivation is:

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 … with 6 decimal digits

https://webmachinelearning.github.io/writing-assistance-apis/#note-download-progress-fraction

[bsmth]

@Josh-Cena do you want to have another look? I've made a deeper tidy at 9291ddb.

Some of the bytes-specific wording was added here:

• Add note about ProgressEvent.loaded reporting different values depending on the browser #32781

[Josh-Cena]

If I understand correctly, for ProgressEvents dispatched by the browser you still get sizes in bytes; for ProgressEvents created by yourself (which I'm not even sure happens a lot) you can plug in any number you want, not just 0–1 normalized. Perhaps you want to make that even clearer...? Leaving my +1

[bsmth]

If I understand correctly, for ProgressEvents dispatched by the browser you still get sizes in bytes; for ProgressEvents created by yourself (which I'm not even sure happens a lot) you can plug in any number you want, not just 0–1 normalized. Perhaps you want to make that even clearer...? Leaving my +1

Yeah that's right, let me go over once again to make sure it's clear, tnx

[bsmth]

I think this is good enough for a merge now to land the improvements. I may call this out for another set of eyes, too. Thanks, Josh 👍🏻