On Wed Feb 22 11:32:26 2023 +0000, Jacek Caban wrote:
It doesn't make sense to return more progress than the event itself
has *before* the event is dispatched, so it has to wait. Why it doesn't make sense? What's wrong with it? I'm trying to understand why do you insist on complicating the implementation and I don't see where this assumption comes from.
From what I can see, when a progress event is dispatched, the progress is always updated compared to what was before. It's not just Gecko's implementation, polyfills also do this, e.g: https://github.com/wisniewskit/FirefoxSynchronousXHRPolyfix/blob/master/Fire...
But in such scenario above, if I remove the responseText handling, Gecko could potentially return the entire text string, without readyState event being sent yet, nor progress event. Later we dispatch those events, and we have the "same" progress, which feels wrong.
I don't know, just feels wrong to me; I could potentially split it into a separate patch. Not sure if that's any better? Or do you still want me to remove it completely?