This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Back to bug 28096
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| seth | 2015-02-24 22:28:30 UTC | CC | seth | |
| zcorpan | 2015-02-26 10:40:19 UTC | CC | ian, simonp | |
| Component | HTML | HTML - <img> | ||
| Assignee | ian | simonp | ||
| QA Contact | contributor | |||
| seth | 2015-03-17 21:56:28 UTC | Summary | Why should we not fire the progress and loadend events for multipart/x-mixed-replace image streams? | Fire the loadend event (and possible progress events) for multipart/x-mixed-replace image streams |
| mike | 2015-09-16 12:39:58 UTC | Component | HTML - <img> | HTML |
| zcorpan | 2015-09-16 12:50:21 UTC | Summary | Fire the loadend event (and possible progress events) for multipart/x-mixed-replace image streams | <img> Fire the loadend event (and possible progress events) for multipart/x-mixed-replace image streams |
| zcorpan | 2016-01-13 10:24:52 UTC | Flags | needinfo?(seth) | |
| josh | 2016-01-29 23:46:38 UTC | CC | josh | |
| hoangminh120814 | 2016-07-20 22:57:04 UTC | OS | other | All |
| QA Contact | contributor | |||
| Assignee | simonp | ian | ||
| d | 2019-03-29 21:35:58 UTC | Resolution | --- | WONTFIX |
| CC | d | |||
| Status | NEW | RESOLVED |
Back to bug 28096