[Mac] Web page scrolls when scrolling through hello conversations

RESOLVED WONTFIX

Status

()

Core
Panning and Zooming
P3
normal
RESOLVED WONTFIX
2 years ago
2 years ago

People

(Reporter: bogdan_maris, Unassigned)

Tracking

Trunk
All
Mac OS X
Points:
---

Firefox Tracking Flags

(firefox47 wontfix, firefox48 wontfix, firefox49 wontfix, firefox50 wontfix, firefox51 wontfix)

Details

(Whiteboard: [gfx-noted])

[Note]:
- this is a followup of bug 1208382

[Affected versions]:
- Firefox 48 beta 2
- latest Developer Edition 49.0a2
- latest Nightly 50.0a1

[Affected platforms]:
- Mac OS X 10.10.5
- Mac OS X 10.9.5

[Unaffected platforms]:
- Mac OS X 10.11

[Steps to reproduce]:
1. Start Firefox
2. Visit a page that can be scrolled
3. Click Hello icon
4. Open many conversations until scrollbar appears in Hello panel
5. Scroll through conversations

[Expected result]:
- The webpage does not scroll when scrolling through hello conversations

[Actual result]:
- Scroll keeps bouncing between webpage and hello conversations list

[Regression range]:
- Not a regression. I can reproduce this since APZ was enabled on OS X nightly

[Additional notes]:
- Even though in bug 1208382 I tested on a build from 2015-11-10 and said that it was fixed, I retested now and it's not...
- This issue happens only if layers.async-pan-zoom.enabled is set to true and only with e10s enabled.
(In reply to Bogdan Maris, QA [:bogdan_maris] from comment #0)
> [Additional notes]:
> - Even though in bug 1208382 I tested on a build from 2015-11-10 and said
> that it was fixed, I retested now and it's not...

AFAIK the Hello code can be updated independently of the Firefox build. It could be that back when you tested the 2015-11-10 build, the Hello code being used didn't have the problem, but now it does. In which case it would be more useful to bisect the Hello code rather than the Firefox code.

ni? to Mark - Is my comment correct? And if so, is there a way to bisect the Loop client code?
Flags: needinfo?(standard8)

Updated

2 years ago
Whiteboard: [gfx-noted]
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #1)
> ni? to Mark - Is my comment correct? And if so, is there a way to bisect the
> Loop client code?

I very much doubt its the loop client code. The 2015-11-10 build would have been before we were outside of the Firefox tree, so you're looking at the hg source for mozilla-central and that's it.
Flags: needinfo?(standard8)
status-firefox47: affected → wontfix
status-firefox48: affected → wontfix
status-firefox49: affected → fix-optional
Priority: -- → P3

Comment 3

2 years ago
Probably is this the same problem and is related: I noticed the same issue with tabs list. I could not find any clear STR or understand in which situation is this happening.

I noticed it around ten days before now if this can help.
Hello is dead, so this is a WONTFIX.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
status-firefox49: fix-optional → wontfix
status-firefox50: affected → wontfix
status-firefox51: --- → wontfix
Resolution: --- → WONTFIX

Comment 5

2 years ago
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #4)
> Hello is dead, so this is a WONTFIX.

As stated above, I already noticed this exact same behavior with the tab list instead of the Hello component. Some people on IRC told me to follow this bug as this seemed to be the same bug.
This strange behavior is still visible. Can we reopen it? Or is it necessary to file a new bug?

On the second case, I don't have much more informations than observing this behavior from time to time.
Flags: needinfo?(bugmail)
(In reply to Clément Lefèvre from comment #5)
> Or is it necessary
> to file a new bug?

I would prefer filing a new bug to avoid confusion. Please provide as much detail as you can in terms of what you are doing when you see this - where the mouse is, where you are scrolling, etc. It sounds like you only encounter this randomly but still, the more information you can provide the easier it will be to figure out.
Flags: needinfo?(bugmail)
You need to log in before you can comment on or make changes to this bug.