982489 - Mapbox demo totally unusable in Firefox, works in the default browser (SkiaGL)

Status: RESOLVED WORKSFORME

(Firefox for Android Graveyard :: Toolbar, defect)

Description

[Marco Castelluccio [:marco]]

I'd guess this is a graphics problem.

Comment 1

[Marco Castelluccio [:marco]]

gfx.canvas.azure.accelerated=false fixes the problem.

I'm running into a similar problem with ptolemy (https://github.com/fzzzy/ptolemy).
Both mapbox and ptolemy use leaflet.

This is reproducible on a Samsung Galaxy S2 (the ptolemy problem was also reproducible on a keon if I recall correctly, and it was fixed by disabling hardware acceleration).

Comment 2

[Aaron Train [:aaronmt]]

Can't find a meta SkiaGL issues back to track this against

Comment 3

[James Willcox (:snorp) ([e-mail]) (he/him)]

What does "totally unusable" mean? It looks alright on Nightly right now.

Comment 4

[Donovan Preston [:fzzzy]]

With Ptolemy on Firefox OS, the problem shows up as most tiles simply not rendering completely. The issue goes away if I turn off hardware acceleration.

I reproduced it on Firefox OS 1.3 on TCL and Nexus 4.

(To test on Firefox OS, get a checkout of Ptolemy and use the App Manager to add a packaged app, choosing the Ptolemy checkout.)

Comment 5

[James Willcox (:snorp) ([e-mail]) (he/him)]

Ok, can you test on Firefox OS using master? I think we fixed this as part of the new Skia rebase (bug 910754) or the single GLContext work (bug 939276).

Comment 6

[Donovan Preston [:fzzzy]]

Ok, will do. Thanks.

Comment 7

[Marco Castelluccio [:marco]]

(In reply to James Willcox (:snorp) ([e-mail]) from comment #3)
> What does "totally unusable" mean? It looks alright on Nightly right now.

On Android, the rendering stops as soon as you interact with the map.

Comment 8

[James Willcox (:snorp) ([e-mail]) (he/him)]

(In reply to Marco Castelluccio [:marco] from comment #7)
> (In reply to James Willcox (:snorp) ([e-mail]) from comment #3)
> > What does "totally unusable" mean? It looks alright on Nightly right now.
> 
> On Android, the rendering stops as soon as you interact with the map.

With Nightly? Which devices? It's working fine here on Nexus 4.

Comment 9

[Marco Castelluccio [:marco]]

(In reply to James Willcox (:snorp) ([e-mail]) from comment #8)
> (In reply to Marco Castelluccio [:marco] from comment #7)
> > (In reply to James Willcox (:snorp) ([e-mail]) from comment #3)
> > > What does "totally unusable" mean? It looks alright on Nightly right now.
> > 
> > On Android, the rendering stops as soon as you interact with the map.
> 
> With Nightly? Which devices? It's working fine here on Nexus 4.

I haven't tested yet on Nightly, it's Firefox 82.

Comment 10

[James Willcox (:snorp) ([e-mail]) (he/him)]

(In reply to Marco Castelluccio [:marco] from comment #9)
> (In reply to James Willcox (:snorp) ([e-mail]) from comment #8)
> > (In reply to Marco Castelluccio [:marco] from comment #7)
> > > (In reply to James Willcox (:snorp) ([e-mail]) from comment #3)
> > > > What does "totally unusable" mean? It looks alright on Nightly right now.
> > > 
> > > On Android, the rendering stops as soon as you interact with the map.
> > 
> > With Nightly? Which devices? It's working fine here on Nexus 4.
> 
> I haven't tested yet on Nightly, it's Firefox 82.

Ok, the (alleged) fixes landed recently, so they will only be in Nightly right now.

Comment 11

[Marco Castelluccio [:marco]]

(In reply to James Willcox (:snorp) ([e-mail]) from comment #10)
> (In reply to Marco Castelluccio [:marco] from comment #9)
> > (In reply to James Willcox (:snorp) ([e-mail]) from comment #8)
> > > (In reply to Marco Castelluccio [:marco] from comment #7)
> > > > (In reply to James Willcox (:snorp) ([e-mail]) from comment #3)
> > > > > What does "totally unusable" mean? It looks alright on Nightly right now.
> > > > 
> > > > On Android, the rendering stops as soon as you interact with the map.
> > > 
> > > With Nightly? Which devices? It's working fine here on Nexus 4.
> > 
> > I haven't tested yet on Nightly, it's Firefox 82.
> 
> Ok, the (alleged) fixes landed recently, so they will only be in Nightly
> right now.

Works in Nightly! (clearly it was Firefox 28, not 82)

Comment 12

[Aaron Train [:aaronmt]]

Fixed on trunk (m-c); should see this fixed with Firefox 30