This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27484 - <img> How should .complete interact with pending requests?
Summary: <img> How should .complete interact with pending requests?
Status: RESOLVED MOVED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other All
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: https://html.spec.whatwg.org/#pending...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-02 15:26 UTC by contributor
Modified: 2019-03-29 20:39 UTC (History)
6 users (show)

See Also:

Attachments

Description contributor 2014-12-02 15:26:14 UTC 
Specification: https://html.spec.whatwg.org/multipage/embedded-content.html
Multipage: https://html.spec.whatwg.org/multipage/#pending-request
Complete: https://html.spec.whatwg.org/#pending-request
Referrer: https://html.spec.whatwg.org/multipage/

Comment:
How should .complete interact with pending requests?

Posted from: 64.134.142.35
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:37.0) Gecko/20100101 Firefox/37.0
Comment 1 Boris Zbarsky 2014-12-02 15:28:46 UTC 
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...
Comment 2 Simon Pieters 2014-12-02 19:01:08 UTC 
See https://www.w3.org/Bugs/Public/show_bug.cgi?id=26113
Comment 3 Domenic Denicola 2019-03-29 20:39:33 UTC 
https://github.com/whatwg/html/issues/4475