Side navigation
#10240 closed bug (cantfix)
Opened September 09, 2011 09:37PM UTC
Closed September 10, 2011 06:18PM UTC
CSS background-image attribute for detached elements does not update in Chrome
Reported by: | lordjmann@gmail.com | Owned by: | lordjmann@gmail.com |
---|---|---|---|
Priority: | undecided | Milestone: | None |
Component: | unfiled | Version: | 1.6.4rc1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
It took me literally forever to track this bug down, as it was not reproduced in non-chrome. If you detach an element (say a span/div) that has a background-image property already set, and attempt to change it while it is detached, it will NOT update. However other CSS properties such as width/height update as expected.
Steps to reproduce:
1.) Create any element, assign it a background-image
2.) Attach/insert element into your page somewhere
3.) Detach element
4.) Attempt to change background-image
Attachments (0)
Change History (4)
Changed September 09, 2011 09:38PM UTC by comment:1
Changed September 10, 2011 01:48AM UTC by comment:2
owner: | → lordjmann@gmail.com |
---|---|
status: | new → pending |
Thanks for taking the time to contribute to the jQuery project! Please provide a complete reduced test case on jsFiddle to help us assess your ticket. If this only occurs on one browser, the problem may not be in jQuery; please try to create a test case that uses only plain Javascript and DOM.
Additionally, be sure to test against the jQuery Edge version to ensure the issue still exists. To get you started, use this boilerplate: http://jsfiddle.net/FrKyN/ Open the link and click to "Fork" (in the top menu) to get started.
Changed September 10, 2011 05:58AM UTC by comment:3
status: | pending → new |
---|
Well, it appears that this is specific to chrome:
jQuery test: http://jsfiddle.net/FrKyN/31/
Regular JS+DOM test: http://jsfiddle.net/9XBEA/
Both exhibit the same problem
Changed September 10, 2011 06:18PM UTC by comment:4
resolution: | → cantfix |
---|---|
status: | new → closed |
Sounds like you'll need to report it to the Chrome team.
This should be for 1.6.1, however I think the problem still persists.