Filed at bz's request in bug 521497 comment 16. We have to, or at least had to, be careful in ClearCurrentRequest() and ClearPendingRequest() in nsImageLoadingContent because of some abuse of aReason over in nsImageLoadingContent (grep for "abuse" in nsImageLoadingContent.cpp). We should figure out if this is still necessary, and if so, clean up nsImageFrame so that it isn't.
I don't think this is an imagelib bug, but I could be wrong.
Component: ImageLib → Layout: Images
QA Contact: imagelib → layout.images
You need to log in before you can comment on or make changes to this bug.