Build: * Device: Otoro * Gaia: 0ec99508cc5198ff0908a85ab624f8bf08f28e31 * Mozilla Central: 0ce1f32125257961232c65c7d6251314f9e0f2be Steps: 1. Go to http://pearce.org.nz/fullscreen/ in the browser 2. Select fullscreen 3. Start scrolling back and forth on the page Expected: The blue div should not be scrollable, but the red div should be scrollable. Upon scrolling only the red div content shall therefore move. Actual: See http://dl.dropbox.com/u/1827165/VID_20120912_174035.mp4 for a demonstration. The blue div which shouldn't be scrollable, ends up being scrollable and holds the highest z-index on top of everything. When you begin scrolling the page, the blue div starts to "overscroll" like behavior (when you stop scrolling, it does a bounce-back like behavior). In comparing this behavior on Android, the behavior is entirely different here and clearly doesn't look right.

Seems like a blocker.

Cody, can you take a look here, please?

I spoke to roc about this and he suggested that the problem may be that either AsyncPanZoomController::SetPageRect() or AsyncPanZoomController::UpdateViewportSize() aren't being called at appropriate times.

Yeah, I've seen some cases just like this in my overscroll work. I'll jump on this as soon as I'm done with that stuff.

Cody: Any news here?

Is there reason to believe this is going to be a common occurrence on websites? Does this affect all fullscreen websites?

FWIW, I can reproduce on my Otoro with the 2012-10-15 build.

Have you had a chance to take a look yet, Cody?

Unassigned to give someone else a chance since Cody peeled off of the overscroll work to focus on Gaia/email.

Milestoning for C2 (deadline of 12/10), as this meets the criteria of "known P2 bugs found before or during C1".

It's been several weeks without any material update here. What needs to happen to fix this?

I have been fixing other scrolling bugs. Looking at this one now.

Suspected dup of bug 814252.

In fact, I'm going to go ahead and dup because I'm 99.9% sure.

Clearing blocking flag for dup.

(In reply to Chris Jones [:cjones] [:warhammer] from comment #14) > In fact, I'm going to go ahead and dup because I'm 99.9% sure. > > *** This bug has been marked as a duplicate of bug 814252 *** I can still reproduce this bug, even though bug 814252 has landed.

FYI - We've switched to using tef? and tracking-b2g? now. basecamp? stopped being used as of Friday 1pm.

I thought it was a dup of bug 797633, I guess I was wrong.

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven't been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.