Closed Bug 876705 Opened 12 years ago Closed 10 years ago

e.me apps do not use asyncPanZoom

Categories

(Firefox OS Graveyard :: Gaia::Everything.me, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: vingtetun, Assigned: ranbena)

References

Details

(Whiteboard: [NPOTB])

It seems like the isExternal call in everything.me/js/Brain.js always returns false and so apps like Google news result into an application that does not use mozasyncpanzoom and are mostly unusable on the device. This is true for most of the news app I have tried and I assume this is true for other apps as well. This isExternal value is returned by a remote server so that does not require code changes in Gaia but I want to make sure to track it.
Adding, e.me people to the bug and marking it as NPOTB
blocking-b2g: tef? → tef+
Whiteboard: [NPOTB]
Joey, can you make sure this gets assigned appropriately? Thanks!
Assignee: nobody → joey
Assignee: joey → ran
Only results from "the wild" which are general web results (usually display the earth icon) get mozAsyncPanZoom. That's cause their mobile compatibility is unpredictable. Indexed results are moderated and overgone a quality process to ensure they are mobile compatible. France is not yet a territory covered by our quality process, therefore it's possible that indexed apps may seem off. Google News is a good example - in France, Google News users are redirected (by Google) to a non-mobile optimized site.
No longer tef blocking. Pulling blocking flag.
blocking-b2g: tef+ → ---
Vivien, we have had France as a supported territory for quite some time. Can you quick test it and resolve the ticket if all is ok?
Flags: needinfo?(21)
It still don't on my device. Not sure why. With APZ turned on for 1.3 we will always use asyncPanZoom anyway.
Depends on: gaia-apzc
Flags: needinfo?(21)
Vivien, can we close this?
Flags: needinfo?(21)
Works for me now.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(21)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.