401
edits
Accessibility/Experiment1 feedback: Difference between revisions
Jump to navigation
Jump to search
Accessibility/Experiment1 feedback (view source)
Revision as of 04:05, 6 October 2009
, 6 October 2009reply on fetch() function
(added replies to many issues) |
(reply on fetch() function) |
||
| Line 124: | Line 124: | ||
* PJ: I think that the fetch and error mechanism might be overkill, how about letting the UA decide if/when to download the resources? You might still want a fetched property I guess, but we might reuse the [http://www.whatwg.org/specs/web-apps/current-work/multipage/embedded-content-0.html#dom-img-complete complete property and onload event from the img element]. | * PJ: I think that the fetch and error mechanism might be overkill, how about letting the UA decide if/when to download the resources? You might still want a fetched property I guess, but we might reuse the [http://www.whatwg.org/specs/web-apps/current-work/multipage/embedded-content-0.html#dom-img-complete complete property and onload event from the img element]. | ||
::: SP reply: the fetch() function | ::: SP reply: we could remove the fetch() function. All I wanted to avoid was to have all files downloaded even if they're not ever required. | ||
* PJ: Making enabled writable would remove the need for enable()/disable(). | * PJ: Making enabled writable would remove the need for enable()/disable(). | ||