User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 Build ID: 20160105164030 Steps to reproduce: We're using etags to validate cached images. We've noticed an issue specific to Firefox when viewing inline svg images after they've been updated. 1. Embed an svg image in a web page using an <img> tag. 2. Update svg file on the server. 3. Hit the image url directly. Etag validation fails, and the new version of the image is returned. 3. Now refresh the web page. The old version of the svg image is still shown. Actual results: Inline svg images are not updated. The cached version of the file is correct, but the rendered svg still shows the old version. A hard refresh, or closing the browser, fixes the issue. Expected results: When the cached version of the svg file is updated, the inline version should update as well. It's my understanding that a rasterized version of the rendered svg image is stored in the surface cache, so that it does not need to be re-rendered on every page view. It seems that hitting the image url directly is updating the file cache, but not invalidating the surface cache.
3 years ago
Component: Untriaged → SVG
Product: Firefox → Core
Could you provide a live testcase (like a button to update a new svg file)?
Live test case: Username: firstname.lastname@example.org Password: test123 1. Go to https://umbriel.igloocommunities.com/documents/firefox_svg_bug and sign in. 2. The SVG file is visible inline on this page, above the document listing. 3. In another tab, go to https://umbriel.igloocommunities.com/documents/firefox_svg_bug/samplesvg?action=versions 4. Click 'select files form my computer' and upload a new svg file. 5. Click 'save'. 6. Immediately go to https://umbriel.igloocommunities.com/download/documents/firefox_svg_bug/samplesvg?attachment=0 7. Now reload the first page you visited: https://umbriel.igloocommunities.com/documents/firefox_svg_bug You should see the old version of the image displayed on this page until you do a hard refresh.
I'm able to reproduce the issue. Do you know if it worked normally in the past with previous versions of Firefox? (FF40/38 e.g.)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.