Community
Participate
Working Groups
Created attachment 157606 [details] test snippet To reproduce, execute snippet using fancy-design, click button.
What we know so far: - The image is set as a source on the svg-image node. - Chrome sends a succesfull request to load the image. - So far there is no difference to loading the image using HTML/DOM. - Now Chrome sends a SECOND request. - This request looks identical to the initial request (like pressing F5). - This causes the session to be killed. - With the next AJAX-request, the response is the index.html Noteworthy: - Safari does not have this problem, even though it also uses webkit. - The url is set on the svg-image using xLink (there is no other way): node.setAttributeNS( "http://www.w3.org/1999/xlink", "href", value ); - The second (bad) request is not logged by the developer tools of Chrome.
Created attachment 157609 [details] fix / workaround Prevents the problem by loading the image using HTML/DOM first.
Applied patch to CVS HEAD.
This issues resurfaced in 1.4M4.
*** Bug 332850 has been marked as a duplicate of this bug. ***
The workaround still does what it should do, but in some cases a second request is created anyway. Also, i found the chrome bug entry for this: http://code.google.com/p/chromium/issues/detail?id=53581
Workaround isn't effective because the shape is not in dom when setting the background-image.
Fixed in CVS HEAD.
*** Bug 333858 has been marked as a duplicate of this bug. ***