Open Bug 583385 Opened 14 years ago Updated 2 years ago

Remove AutoStateChanger depth-counting machinery from nsImageLoadingContent

Categories

(Core :: Graphics: ImageLib, defect)

Product:
Core
Component:
Graphics: ImageLib
Type:
defect

Tracking

()

People

(Reporter: bholley, Unassigned)

References

(Depends on 1 open bug)

Details

It's gross. Now that image observer events are asynchronous (bug 572520), we don't need it anymore. Really though, we should wait until bug 580466 is fixed. It could simplify things a lot.
Er, we still need AutoStateChanger, we just don't need the depth-counting machinery. And thinking about it more, it won't simplify things all that much. But we should still do it - maybe do an interim patch where we assert the depth never gets past 1?
Summary: Remove AutoStateChanger machinery from nsImageLoadingContent → Remove AutoStateChanger depth-counting machinery from nsImageLoadingContent
It wouldn't simplify things, but it'd save some memory...
Depends on: 580466
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.