User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20100101 Firefox/17.0 Build ID: 20121128204232 Steps to reproduce: yesterday i upgraded to firefox 17.01. Actual results: in 17.01 content does not refresh completely. i started firefox in safe mode but still i have this issue. i have developed an online builder for a client and now the pages must be refreshed to reload all new content. note that this only happens in firefox and no other browsers. also this only happens in17.01. Expected results: all content should have refreshed.

Can you attach a testcase or a public URL and post steps to reproduce ?

In addition could you try with a fresh profile (don't import anything): https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

(In reply to Matthias Versen (Matti) from comment #1) > Can you attach a testcase or a public URL and post steps to reproduce ? attached is a short movie of the issue: Attachment #695239 [details] the issue is that background images do not refresh 1st time. must refresh browser 2 times to refresh background images. i have tested this about 50 times and the result is the same eveytime.also it does not occur in any other browser. therefore i think there is a bug in firefox 17.01 that is the reason. also you can recreate by going to http://builder.ikomee.com user: test@tt00.com pass: test1

(In reply to Loic from comment #2) > In addition could you try with a fresh profile (don't import anything): > https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove- > firefox-profiles i uninstalled firefox and all profile data and did a fresh install. the issue is still there. i will bet my new pencil :) that this is a bug in firefox. also please see my reply to Matti which is listed above as comment 4. this issue is regarding background images only and i have attached a test case for your viewing.

STR: 1) open http://builder.ikomee.com 2) login using user: test@tt00.com , pass: test1 3) click on "list sites" 4) click "edit template" 5) move the mouse on the "category" section on left side and select "edit box color" 6) change the color with the color palette on the right side and hit submit 7) click the "update preview" button on the top 8) the color doesn't change 9) click the button from 7) again and it changes

Thanks for the STR. :) There are 2 regressions: Regression #1: After clicking on "update preview", the color changes only if the user hovers with his mouse the page content (left pane "category"). m-c good=2012-06-27 bad1=2012-06-27 http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=5cdbeae14405&tochange=bf8f2961d0cc Regression #2: It's the current behavior, the user needs to click twice on "update preview" to change the color. m-c bad1=2012-08-15 bad2=2012-08-16 http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=86ee4deea55b&tochange=50e4ff05741e Need more investigation!

I can confirm the regression range (forgot to post) and I'm currently trying to bisect regression #1

Regression #1 window Good: http://hg.mozilla.org/integration/mozilla-inbound/rev/06e7df3a8209 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/16.0 Firefox/16.0 ID:20120627083614 Bad #1: http://hg.mozilla.org/integration/mozilla-inbound/rev/7ef9568fbd40 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/16.0 Firefox/16.0 ID:20120627084814 Pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=06e7df3a8209&tochange=7ef9568fbd40 Suspected #1: Bug 758620 Regression #2 window Bad #1: http://hg.mozilla.org/mozilla-central/rev/3b46b03dff5c Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0 ID:20120815053101 Bad #2: http://hg.mozilla.org/mozilla-central/rev/d67c02074ced Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0 ID:20120815065301 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=3b46b03dff5c&tochange=d67c02074ced In loca build Last Bad #1: 5709499c7c66 First Bad #2: 5c730c1f2274 +d5e42dcb36fd+d67c02074ced Regression #2 by : 5c730c1f2274 Kyle Huey — Bug 697230: Part 1 - Centralize style image observers. r=bz

local build Last Good: 2866469094c3 First Bad#1: 4d177002f473 Triggered by 4d177002f473 Chris Lord — Bug 758620 - Force fixed-position frames to have their own layers. r=roc Introduce a new display-list item 'nsDisplayFixedPosition' that represents fixed-position elements. This item cannot be merged, which forces fixed position elements to have their own layer, and has a BuildLayer implementation that sets the necessary metadata on a Layer to be able to maintain its position correctly during composition when asynchronously panning and zooming.

Not tracking for FF18 at this time as we are not sure of any major website regressions & have already released 18.0b6 at this time. CC'ing Chris to request help with investigation here as comment 10 suggests 758620 may have regressed this.

The severity of this issue is not great enough to track for release, and is easily worked around. We would accept a low risk uplift once resolved, however.

(In reply to Alex Keybl [:akeybl] from comment #12) > The severity of this issue is not great enough to track for release, and is > easily worked around. We would accept a low risk uplift once resolved, > however. this issue is very relevant for me as it affects my entire website app. you speak as if this issue is of no consequence, but it is to me. you say this is easily worked around so you obviously know the appropriate workarounds...please tell me what workarounds you are referring to. p.s i am disappointed with the mozilla community. you have a bug in your software that did not exist previously and with the huge amount of resources available at your disposal you cannot or will not fix this bug. if it affected one of googles products then it would have been fixed immediately. google is like all other corporates in this world; money is the primary purpose and cause for everything. :(

I think this is likely a duplicate of bug 815270. Given we're releasing 18 next week, and that the fix suggested in that bug has the downside of breaking other cases on mobile, I don't think this is worth addressing. (In reply to russ131313 from comment #13) > (In reply to Alex Keybl [:akeybl] from comment #12) > > The severity of this issue is not great enough to track for release, and is > > easily worked around. We would accept a low risk uplift once resolved, > > however. > > this issue is very relevant for me as it affects my entire website app. you > speak as if this issue is of no consequence, but it is to me. you say this > is easily worked around so you obviously know the appropriate > workarounds...please tell me what workarounds you are referring to. I'm sorry this has affected you, but this should be fixed in Firefox 18 which is released next week. It would be useful if you could test this. > p.s i am disappointed with the mozilla community. you have a bug in your > software that did not exist previously and with the huge amount of resources > available at your disposal you cannot or will not fix this bug. if it > affected one of googles products then it would have been fixed immediately. > google is like all other corporates in this world; money is the primary > purpose and cause for everything. :( I'm sorry you feel this way. Contrary to what you say, we don't have a huge amount of resources, and given the time of year (Christmas, New Year), many of us have been taking time off (including myself) and so things like this may have slipped a little more than usual. I'm not sure that your statement about Google is true either, as Chrome has several unaddressed bugs that have been present for a long time. I'm sure they try their hardest though, as do we. Do remember that you are part of this community too. A reduced test-case goes a long way to solving issues like this, and this is somewhere that you could contribute. Please let us know if this is not fixed in Firefox 18. You can test this already by downloading the beta from http://www.mozilla.org/beta

(In reply to Chris Lord [:cwiiis] from comment #14) > I think this is likely a duplicate of bug 815270. Given we're releasing 18 > next week, and that the fix suggested in that bug has the downside of > breaking other cases on mobile, I don't think this is worth addressing. > > (In reply to russ131313 from comment #13) > > (In reply to Alex Keybl [:akeybl] from comment #12) > > > The severity of this issue is not great enough to track for release, and is > > > easily worked around. We would accept a low risk uplift once resolved, > > > however. > > > > this issue is very relevant for me as it affects my entire website app. you > > speak as if this issue is of no consequence, but it is to me. you say this > > is easily worked around so you obviously know the appropriate > > workarounds...please tell me what workarounds you are referring to. > > I'm sorry this has affected you, but this should be fixed in Firefox 18 > which is released next week. It would be useful if you could test this. > > > p.s i am disappointed with the mozilla community. you have a bug in your > > software that did not exist previously and with the huge amount of resources > > available at your disposal you cannot or will not fix this bug. if it > > affected one of googles products then it would have been fixed immediately. > > google is like all other corporates in this world; money is the primary > > purpose and cause for everything. :( > > I'm sorry you feel this way. Contrary to what you say, we don't have a huge > amount of resources, and given the time of year (Christmas, New Year), many > of us have been taking time off (including myself) and so things like this > may have slipped a little more than usual. > > I'm not sure that your statement about Google is true either, as Chrome has > several unaddressed bugs that have been present for a long time. I'm sure > they try their hardest though, as do we. > > Do remember that you are part of this community too. A reduced test-case > goes a long way to solving issues like this, and this is somewhere that you > could contribute. > > Please let us know if this is not fixed in Firefox 18. You can test this > already by downloading the beta from http://www.mozilla.org/beta i have tested FF18.0b7 and the bug persists, hence my frustration. i am concerned as the comments from Chris suggest that this issue will not be addressed in FF18. however i do apologize for my rant. (In reply to Chris Lord [:cwiiis] from comment #14) > I think this is likely a duplicate of bug 815270. Given we're releasing 18 > next week, and that the fix suggested in that bug has the downside of > breaking other cases on mobile, I don't think this is worth addressing. > > (In reply to russ131313 from comment #13) > > (In reply to Alex Keybl [:akeybl] from comment #12) > > > The severity of this issue is not great enough to track for release, and is > > > easily worked around. We would accept a low risk uplift once resolved, > > > however. > > > > this issue is very relevant for me as it affects my entire website app. you > > speak as if this issue is of no consequence, but it is to me. you say this > > is easily worked around so you obviously know the appropriate > > workarounds...please tell me what workarounds you are referring to. > > I'm sorry this has affected you, but this should be fixed in Firefox 18 > which is released next week. It would be useful if you could test this. > > > p.s i am disappointed with the mozilla community. you have a bug in your > > software that did not exist previously and with the huge amount of resources > > available at your disposal you cannot or will not fix this bug. if it > > affected one of googles products then it would have been fixed immediately. > > google is like all other corporates in this world; money is the primary > > purpose and cause for everything. :( > > I'm sorry you feel this way. Contrary to what you say, we don't have a huge > amount of resources, and given the time of year (Christmas, New Year), many > of us have been taking time off (including myself) and so things like this > may have slipped a little more than usual. > > I'm not sure that your statement about Google is true either, as Chrome has > several unaddressed bugs that have been present for a long time. I'm sure > they try their hardest though, as do we. > > Do remember that you are part of this community too. A reduced test-case > goes a long way to solving issues like this, and this is somewhere that you > could contribute. > > Please let us know if this is not fixed in Firefox 18. You can test this > already by downloading the beta from http://www.mozilla.org/beta i have tested FF18.0b7 and the bug persists, hence my frustration. i am concerned as the comments from Chris suggest that this issue will not be addressed in FF18. however i do apologize for my rant.

It surprises me this isn't fixed in Firefox 18 :/ Cc'ing Matt Woodrow for comment, I think he's in a better position than me to know what this might be. This may still be fixed in Firefox 17 by bug 815270. Do we know if this happens in Firefox 19 or 20? A reduced test case (i.e. the smallest possible page that reproduces this bug) would be very helpful.

this bug is also in firefox 19. i have been waiting and hoping it will be fixed but unfortunately not yet. is this bug going to be fixed or not? i need to know as it affects my app. this week i finished building my app and i am ready to launch it now, i.e spend money on advertising, but this firefox bug is an issue for me. please let me know what is happening.

does anyone know a work around for this bug. i have tried everything i can think of and i am completely out of ideas. please, i need some help in coming up with some kind of solution as it does not appear as if this bug is going to be fixed.

no worries...found a suitable work around

The page appears to have changed, and no longer has the content in the original report. We'd need another test case to be able to do anything with this sorry.

Reporter, do you know when your website (showing the issue) will be back from maintenance?

(In reply to Loic from comment #21) > Reporter, do you know when your website (showing the issue) will be back > from maintenance? i worked around the issue so it is no longer possible to view the issue. this is no longer an issue for me! however i can setup a test case with the issue, if you require...let me know. p.s while updating i overwrote some files i needed, so i am fixing now. builder will be back online by monday. its been one of those weeks.

Having a standalone test case would be *very* useful! Whenever you're able. :)

Assuming a testcase is still needed here based on comment 23. That said, does this still reproduce in the current Firefox Nightly?

(In reply to Anthony Hughes (:ashughes) [GFX][QA][Mentor] from comment #24) > Assuming a testcase is still needed here based on comment 23. That said, > does this still reproduce in the current Firefox Nightly? This bug still needs a testcase and/or verification that this bug is still reproducible. If no response is given in two weeks this bug will be closed as incomplete.

Resolved per whiteboard