Open Bug 605496 Opened 10 years ago Updated 7 years ago
cached APNG is not animated if it is used only by CSS background-image
Mozilla seems fails to animate an APNG image, if it is cached into the memory and it is used just as a background image by CSS background-image. * If it is the first time I see the image? => OK. Background image is animated. * If the image is cached? => NG. Background image is animated and only the first frame is shown. * If the image is not cached (after I did super-reload by Ctrl-F5)? => OK. Background image is animated. * If there is an <img> refers same image, even if the image is cached? => OK. Background image is animated. The bug 595142 (it was fixed) seems like this problem, but this still happens.
Summary: cached APNG are not animated if it is used only by CSS background-image → cached APNG is not animated if it is used only by CSS background-image
I saw this problem always on this environment: Application Basics Name Firefox Version 4.0b8pre User Agent Mozilla/5.0 (Windows NT 6.0; rv:2.0b8pre) Gecko/20101019 Firefox/4.0b8pre Profile Directory Open Containing Folder Enabled Plugins about:plugins Build Configuration about:buildconfig Modified Preferences Name Value accessibility.typeaheadfind.flashBar 0 browser.link.open_newwindow.restriction.backup 0 browser.link.open_newwindow.restriction.override 2 browser.places.smartBookmarksVersion 2 browser.startup.homepage_override.buildID 20101019031458 browser.startup.homepage_override.mstone rv:2.0b8pre browser.tabs.insertRelatedAfterCurrent false browser.tabs.insertRelatedAfterCurrent.backup false browser.tabs.loadFolderAndReplace false browser.tabs.loadFolderAndReplace.backup false browser.tabs.warnOnClose false dom.report_all_js_exceptions true extensions.checkCompatibility.4.0b false extensions.checkCompatibility.4.0b3 false extensions.lastAppVersion 4.0b8pre general.useragent.extra.microsoftdotnet ( .NET CLR 3.5.30729; .NET4.0C) network.cookie.prefsMigrated true places.history.expiration.transient_current_max_pages 104635 privacy.sanitize.migrateFx3Prefs true Graphics Adapter Description NVIDIA GeForce 9800 GT Vendor ID 10de Device ID 0605 Adapter RAM 512 Adapter Drivers nvd3dum nvwgf2um,nvwgf2um Driver Version 188.8.131.5245 Driver Date 4-3-2010 Direct2D Enabled true DirectWrite Enabled true GPU Accelerated Windows 1/1 Direct3D 9
Testcase 1. Steps to reproduce this problem: 1. save the testcase to the local disk. 2. load it into Minefield. 3. Then, background images are animated correctly. 4. Click "Reload" on the toolbar. Actual: Background images are not animated. Expected: Background images are animated.
Testcase 2, this works correctly because there are <img> tags which refer same APNG images.
Oops. (In reply to comment #0) > * If the image is cached? > => NG. Background image is animated and only the first frame is shown. correct: * If the image is cached? => NG. Background image is *NOT* animated and only the first frame is shown.
Alon - any thoughts on this? What's the status of the animation regressions?
Hmm, this might be related to the other animation bugs. Need a regression range to be sure though. Status: * Looking into bug 601723 right now. * Still waiting for a response on https://bugzilla.mozilla.org/show_bug.cgi?id=594771#c13 * I am starting to suspect that bug 528003 is the underlying cause of several of these issues, both because of what I see in debugging, and source comments like // Note, however, that this doesn't guarantee the behaviour we want (one // URL maps to the same image on a page) if we load the same image in a // different tab (see bug 528003), because its load id will get re-set, and // that'll cause us to validate over the network.
Regression window: Works: http://hg.mozilla.org/mozilla-central/rev/75d2145d1bd3 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b6pre) Gecko/20100907 Firefox/4.0b6pre ID:20100907194131 Fails: http://hg.mozilla.org/mozilla-central/rev/4bb022d84a31 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b6pre) Gecko/20100907 Firefox/4.0b6pre ID:20100907182227 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=75d2145d1bd3&tochange=4bb022d84a31
You need to log in before you can comment on or make changes to this bug.