Closed Bug 1281477 Opened 10 years ago Closed 10 years ago

[Mac] Glitches while scrolling through hello conversations

Categories

(Core :: Layout, defect)

All
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1208437
Tracking Status
firefox47 --- affected
firefox48 --- affected
firefox49 --- affected
firefox50 --- affected

People

(Reporter: bmaris, Unassigned)

Details

[Affected versions]: - Firefox 47.0 - Firefox 48 beta 2 - latest Developer Edition 49.0a2 - latest Nightly 50.0a1 [Affected platforms]: - Mac OS X 10.10.5 [Unaffected platforms]: - Mac OS X 10.11.2 - Mac OS X 10.9.5 [Steps to reproduce]: 1. Start Firefox 2. Start a few hello conversations so the scrollbar appears inside hello panel 3. Scroll through conversations [Expected result]: - No visual defects can be seen [Actual result]: - Glitches are present in hello panel while scrolling [Regression range]: - This is not a regression, it reproduces on old nightly builds (36.0a1). I did search for a regression range though but I get something that points to the implementation of rooms: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=084441e904d1&tochange=b4fbeba78a7d Bug 1099128 - Swap Loop to use rooms rather than call urls So this bug has been there since forever. [Additional notes]: - Not quite sure if this is a hello bug of something graphics related. I also have a feeling I ran into this bug in my early days but could not find the specific bug (if there is any). - Screencast showing the issue is attached.
(In reply to Bogdan Maris, QA [:bogdan_maris] from comment #0) > - Screencast showing the issue is attached. And here is the promised screencast: https://db.tt/8P1Qid6x (to large for uploading to bugzilla)
All we're doing is using a browser that gets display in front of the main window. This feels like some platform type of bug - not correctly accounting for focus/scroll window.
Component: Client → Layout
Product: Hello (Loop) → Core
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.