STR: 1) Open the settings app. 2) Slide to the left (so that content to the right becomes visible) Actual: The wifi section becomes visible. Expected: The user shouldn't be able to scroll horizontally. This needs to block, IMO.

This must be a recent regression. *sigh*

Tim, I can’t reproduce with Gecko 18 and the latest Gaia on my Otoro. Which version of Gecko are you using?

I am able to reproduce it in Unagi. Please try the daily release build from: https://releases.mozilla.com/b2g/ 2012-12-02(recent few builds should be the same result, too) (beta v18 gecko with master gaia) Reproduction Steps: 1. Open the settings app 2. Click anything lead you to the new screen. For example, internet sharing or wifi should be two good ones to be tested. 3. Click "<" to go back to settings 4. hold any option and slide to the left Youtube video is attached for reference: http://www.youtube.com/watch?v=UEdHSR_pHaA&feature=g-upl Hopefully this helps

Oops, now that I think about it entering a sub section is crucial to reproduce this. Sorry for my incomplete STR, kaze. Thank you, Walter!

Tim, no problem. The mechanism of settings is to load the setting sub section after you choose it. And, how it go back to the main setting app is to make the loaded sub section hide is by moving it to -100%. In this case, if you didn't get into a subsection before, there won't be anything for you to horizontally scroll.

(In reply to Walter Chen from comment #5) > The mechanism of settings is to load the setting sub section after you > choose it. And, how it go back to the main setting app is to make the loaded > sub section hide is by moving it to -100%. In this case, if you didn't get > into a subsection before, there won't be anything for you to horizontally > scroll. Sure thing, but I still can’t reproduce it. What Gecko version are you using? FTR, this looks like bug 797411 which has been marked as bb-. To work around this bug we’re using an |overflow: scroll-y| rule in the Settings CSS, which has a high performance cost (~150ms IIRC) and which, apparently, isn’t enough in the case you’re both experiencing.

(In reply to Fabien Cazenave [:kaze] from comment #2) > Tim, I can’t reproduce with Gecko 18 and the latest Gaia on my Otoro. Which > version of Gecko are you using? Can still reproduce with latest Gaia and latest Gecko 18.

(In reply to Walter Chen from comment #3) > (beta v18 gecko with master gaia) Oh, I missed that. My Gecko doesn’t have this bug… > $ adb shell cat /system/b2g/platform.ini > [Build] > BuildID=20121129094217 > Milestone=18.0 > SourceStamp=6e6c2d28ffdf > SourceRepository=http://hg.mozilla.org/releases/mozilla-beta So this looks like a Gecko regression that appeared in the last 3 days. :-(

(In reply to Fabien Cazenave [:kaze] from comment #8) > So this looks like a Gecko regression that appeared in the last 3 days. :-( What's your tip revision? I can go back and try if I can still reproduce it.

(In reply to Tim Taubert [:ttaubert] from comment #9) > (In reply to Fabien Cazenave [:kaze] from comment #8) > > So this looks like a Gecko regression that appeared in the last 3 days. :-( > > What's your tip revision? I can go back and try if I can still reproduce it. GOSH, next time I'll read your whole comment :)

(In reply to Tim Taubert [:ttaubert] from comment #9) > (In reply to Fabien Cazenave [:kaze] from comment #8) > > So this looks like a Gecko regression that appeared in the last 3 days. :-( > > What's your tip revision? I can go back and try if I can still reproduce it. Can't reproduce anymore, that's a regression :|

Caused by bug 805638.

Adding :schien who worked on bug 805638.

+1 for nominating this bug as basecamp-blocker.

Pointer to Github pull-request

Comment on attachment 687751 [details] Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/6784 works perfectly. Thanks!

Comment on attachment 687751 [details] Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/6784 NOTE: If blocking-basecamp+ is set, just land it for now. [Approval Request Comment] Bug caused by (feature/regressing bug #): bug 805638 User impact if declined: broken panel navigation Testing completed: manual Risk to taking this patch (and alternatives if risky): none

Looks good. Thanks for the fix Tim!

The fix unexpectedly cause the problem bug 818056, leave the blocks tag here to know the dependency.