942701 - [Settings] Can't scroll down

Status: RESOLVED DUPLICATE of bug 941310

(Firefox OS Graveyard :: General, defect)

Description

[Walter Chen[:ypwalter][:wachen]]

Devices: Nexus4, Buri
(Doesn't reproduce in Unagi as far as I know)

Reproduce steps:
1. Launch Settings app
2. Scroll down

Expected Rsult:
It scrolls down

Actual Result:
It doesn't scroll down



PS. Bug 938785 might be related.

Comment 1

[Enpei]

Fugu has the problem as well, it should be bug from master build.

Gaia:     671a7c1fae1c32a77b2675636c7efdf089fd6443
Gecko:    b79ea773754854e17566f302e80e2654d9c155c9
BuildID   20131126092608
Version   28.0a1

Comment 2

[Josiah Bruner [:jsbruner]]

This seems to happen on the Email app as well for me. (Nexus 4)

Comment 3

[Enpei]

Today's build are working on Buri and Fugu, but this is often up and down from Monday to today. Will keep monitoring.

Gaia:     087d109c83235fc157b2efac7ace6cc54a4c5aaa
Gecko:    8fdb69114734785065ce6c76ac36f4438b90c2e6
BuildID   20131127093419
Version   28.0a1

Comment 4

[Enpei]

(In reply to Enpei from comment #3)
> Today's build are working on Buri and Fugu, but this is often up and down
> from Monday to today. Will keep monitoring.
> 
> Gaia:     087d109c83235fc157b2efac7ace6cc54a4c5aaa
> Gecko:    8fdb69114734785065ce6c76ac36f4438b90c2e6
> BuildID   20131127093419
> Version   28.0a1

Please ignore my last comment, after reboot device, bug found again. Nominate as v1.3 blocker.

Comment 5

[Walter Chen[:ypwalter][:wachen]]

It's not always happening when first time launched. My buri has the issue after I used it for awhile.

Comment 6

[[:fabrice] Fabrice Desré]

Can you check if the fix is bug 942259 is in your builds?

Comment 7

[Evelyn Hung]

looks like not a settings specific issue.

Comment 8

[Tim Guan-tin Chien [:timdream] (please needinfo)]

Still not working for me, I have verified my build contains patch in bug 942259.

Comment 9

[Vivien Nicolas (:vingtetun) (:21) - (NOT reading bugmails, needinfo? please)]

So it seems like the preallocated process is lying. The check at http://mxr.mozilla.org/mozilla-central/source/dom/browser-element/BrowserElementPanning.js#51 fails because the app says that docShell.asyncPanZoomEnabled == true while we are in the preallocated process.

When the prealocatted process is consume by a real app, this value is correct but it is too late.

I seems like something has changed in the way we initialize the asyncPanZoomEnabled value by default.