Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Avatar for Username

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

Draw bug on background-image inline-css when content is created dynamically

  • 7 wotmołwy
  • 6 ma tutón problem
  • 2 napohladaj
  • Poslednja wotmołwa wot Reitman

daryrace
daryrace
more options

Hey guys,

we recently discovered that the latest Firefox version (19) has a bug that is not painting images correctly when the content is created dynamically (in our case e.g., a JSON is retched by AJAX, which is then used in a underscore Javascript template). The templates contain a inline-style like:

<td style="background-image: url(http://a.cdn.net/path/to/image.png)">...</td>

When I make a full refresh, everything is loaded instantly and looks fine. However, if the content area is cleared and new content is created (in exactly the same way as on a clean refresh, except that the page is not reloaded - so AJAX > JSON > _.underscore), then the pictures are not immediately visible. Sometimes it takes up to 10-12 seconds for them to display.

This ONLY occurs in Firefox 19 and 20b1

Live Example:

https://www.racebets.com/en/horse-betting-online/race/details/id/808582/

Clean refresh, all good. But change the races once loaded, and the silks are not painted.

If you resize the window, change some CSS style or scroll up and down, the silks are painted immediately - so I suspect it is a draw/paint issue.

Any ideas how to prevent this and when it will be fixed?

Hey guys, we recently discovered that the latest Firefox version (19) has a bug that is not painting images correctly when the content is created dynamically (in our case e.g., a JSON is retched by AJAX, which is then used in a underscore Javascript template). The templates contain a inline-style like: <td style="background-image: url(http://a.cdn.net/path/to/image.png)">...</td> When I make a full refresh, everything is loaded instantly and looks fine. However, if the content area is cleared and new content is created (in exactly the same way as on a clean refresh, except that the page is not reloaded - so AJAX > JSON > _.underscore), then the pictures are not immediately visible. Sometimes it takes up to 10-12 seconds for them to display. This ONLY occurs in Firefox 19 and 20b1 Live Example: https://www.racebets.com/en/horse-betting-online/race/details/id/808582/ Clean refresh, all good. But change the races once loaded, and the silks are not painted. If you resize the window, change some CSS style or scroll up and down, the silks are painted immediately - so I suspect it is a draw/paint issue. Any ideas how to prevent this and when it will be fixed?

Wot daryrace změnjeny

Wšě wotmołwy (7)

philipp
philipp
  • Moderator
more options

hello, if you've found a genuine & reproducible bug, please file it at bugzilla.mozilla.org - there it will get the attention of developers. here on the support forums we try to provide solutions to users for common questions & problems, but we are not in the bug-fixing business. thank you...

daryrace
daryrace Prašer
more options

thanks

Reitman
Reitman
more options

I have same problem too. On XP and Seven!

philipp
philipp
  • Moderator
more options

this is now apparently worked upon in bug #844750.

Reitman
Reitman
more options

Is exactly this problem! When mozilla think fix this?

philipp
philipp
  • Moderator
more options

according to the comments in the bug report the fix is targeted for the next beta version of firefox 20 which is going to be built next week.

Reitman
Reitman
more options

In bugzilla they changed status for RESOLVED FIXED. But fixed just in FF 22. So firefox 19 will continue with this bug? I have many sites that not displayed well because this bug!