861669 - [10.7] Implement proper scroll target detection for vertical bounce effect

Status: RESOLVED FIXED

(Core :: Widget: Cocoa, defect)

Description

[Hawken Rives]

Attachment: Screen Shot 2013-04-14 at 1.28.02 PM.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20130414 Firefox/23.0
Build ID: 20130414031025

Steps to reproduce:

Running Nightly (built from http://hg.mozilla.org/mozilla-central/rev/ef802a6418f2) breaks scrolling on the integrated Facebook chat popups.

Running on a 15" Retina MBP.


Actual results:

Scrolling is broken (it's hard to describe.)


Expected results:

Scrolling in the attached chat windows should be independent of scrolling in the browser. I've attached a picture of the popups, just to be clear.

Comment 1

[Hawken Rives]

Just to be clearer: this is only broken after the patch for bug 673875, "Reproduce bounce behaviour when reaching top and bottom of documents."

Comment 2

[Stephen A Pohl [:spohl]]

Opened bug 861748 to disable the synchronous scroll that breaks FB chat when the page bounce behavior is turned off. This bug here should remain open to fix FB chat when the page bounce behavior is actually turned on.

Comment 3

[Stephen A Pohl [:spohl]]

The detection of the scroll target implemented in bug 673875 is not sufficient and causes unexpected bounces in various scenarios. See bug 865563 for another scenario.

Comment 5

[Stefan Arentz | :st3fan | ⏰ EST | he/him]

Here is a public google docs spreadsheet that can be used for testing:

https://docs.google.com/spreadsheet/ccc?key=0AmwZL-gS9ZMmdDhNX3pGNDNHcmcxQ3BxOTFsQ3FfZlE#gid=0

Comment 6

[Stephen A Pohl [:spohl]]

This is fixed by the new patches for bug 673875.

Comment 7

[Christian Sonne [:cers]]

I still seem to be unable to zoom in or out by finger scrolling (up/down) in Google Maps after this change.

Comment 8

[Stephen A Pohl [:spohl]]

(In reply to Christian Sonne [:cers] from comment #7)
> I still seem to be unable to zoom in or out by finger scrolling (up/down) in
> Google Maps after this change.

Are you referring to the new or old Google Maps? I'm currently unable to reproduce this. Either way, could you please file a new bug with clear STR and CC me? Thanks!