1085024 - black background and repeated flashing when rendering map demo

Status: RESOLVED DUPLICATE of bug 1083079

(Core :: Graphics, defect)

Description

[Andreas Gal :gal]

STR.

1. Go to http://leafletjs.com/index.html
2. Zoom out a bit
3. Zoom in again
4. On gecko the background flashes black and tiles disappear repeatedly.

Expected:

4. On Safari there is no flashing and tiles don't disappear.

Comment 1

[John Firebaugh]

This is a severe rendering regression in a widely used JavaScript library; can someone please investigate?

As a starting point, it is almost certainly caused by tiled layers. Disabling layers.enable-tiles in about:config and relaunching Firefox makes the issue disappear.

Comment 2

[Chris Lord [:cwiiis]]

cc'ing some gfx peeps on this - seems like a pretty serious issue to have crept into a release :/

Apparently fixed on trunk? I have no Mac to test this, so can't confirm.

Comment 3

[John Firebaugh]

Confirmed, the issue does not appear in 38.0a1 (2015-01-13).

Comment 4

[Jonathan Watt [:jwatt]]

It also doesn't appear to affect aurora (v36). Perhaps this is caused by the issue that bug 1083079 fixed.

Comment 5

[Vladimir Agafonkin]

(In reply to Jonathan Watt [:jwatt] from comment #4)
> It also doesn't appear to affect aurora (v36). Perhaps this is caused by the
> issue that bug 1083079 fixed.

Looks like it's the same issue, because this is the same we have in Leaflet:

> it turns out this is because [...] the tiles are at negative offsets.

Any idea on when FF 36 lands to stable?

Comment 6

[Robert Longson [:longsonr]]

(In reply to Vladimir Agafonkin from comment #5)
> Any idea on when FF 36 lands to stable?

24th February according to https://wiki.mozilla.org/RapidRelease/Calendar

Comment 8

[John Firebaugh]

Is there any JS or CSS workaround for the issue? It would be a real shame to have all Leaflet maps on the web broken on Mac FF for another month+.

Comment 9

[Jonathan Watt [:jwatt]]

I'm not sure that there is. It's difficult to know when content will trigger this. In a very loose and vague sense it can happen when internally something is layerized and there are negative offsets in some way. I'm not clear on exactly what content will result in negative offsets in the internal code, but things like positioning positioned elements relative to 'bottom' can do it, at least in certain circumstances.