You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not clear to me how .complete should interact with pending requests, because the definition of "complete" is in terms of "completely available" and "completely available" doesn't make it clear whether the data being talked about is the current or pending data.
As a simple proposal, we could make .complete be false if there is a pending request at all...
That sounds nice and simple, but we'd need tests and to ensure it's not too incompatible with current browsers.
Note that .complete is broken in other ways too: #1055
The text was updated successfully, but these errors were encountered:
These changes are in line with all three browsers. Chrome still diverges significantly from the standard & tests though on other aspects.
Tests: web-platform-tests/wpt#19298.
Fixes#1055, fixes#4475. #4476 remains outstanding.
These changes are in line with all three browsers. Chrome still diverges significantly from the standard & tests though on other aspects.
Tests: web-platform-tests/wpt#19298.
Fixes#1055, fixes#4475. #4476 remains outstanding.
These changes are in line with all three browsers. Chrome still diverges significantly from the standard & tests though on other aspects.
Tests: web-platform-tests/wpt#19298.
Fixes#1055, fixes#4475. #4476 remains outstanding.
Ported from https://www.w3.org/Bugs/Public/show_bug.cgi?id=27484, where @bzbarsky says:
That sounds nice and simple, but we'd need tests and to ensure it's not too incompatible with current browsers.
Note that
.complete
is broken in other ways too: #1055The text was updated successfully, but these errors were encountered: