1327286 - [e10s][APZ] Impossible to scroll scrollable area on the page

Status: RESOLVED WORKSFORME

(Core :: Panning and Zooming, defect)

Description

[arni2033]

>>>   My Info:   Win7_64, Nightly 49, 32bit, ID 20160526082509
STR_1:
1. Open http://www.3dnews.ru/901538
2. Scroll the page to the iframe between section "��������� �� ����" and line "���������� URL"
3. Inside the iframe, hover mouse over the scrollbar in scrollable area, rotate mouse wheel down once

AR:  The page scrolls down
ER:  The scrollable area should scroll down

This is a regression. Nightly 2015-09-01 is unaffected, Nightly 2016-05-26 is affected.

Comment 1

[Emil Pasca [:emilpasca]]

I haven't managed to reproduce the issue, after navigating to the provided URL, I haven't found the section mentioned in 2 from STR_1. Could you please provide a screenshot in order to see where is the issue?

Comment 2

[arni2033]

(In reply to Emil Pasca [:emilpasca] from comment #1)
> I haven't managed to reproduce the issue, after navigating to the provided
> URL, I haven't found the section mentioned in 2 from STR_1
Huh, the text is just corrupted... I put updated STR in userstory, try it now.

Comment 3

[Botond Ballo [:botond]]

Attachment: Screenshot of relevant part of page

I'm not seeing an iframe in the mentioned area of the page. Please see the attached screenshot. I see the "Материалы по теме" near the top and the "Постоянный URL" near the bottom, but no iframe.

Comment 4

[Emil Pasca [:emilpasca]]

User Agent:  Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0

I have tested this issue on Windows 10 x64 with the latest Firefox release (50.1.0), latest Nightly (53.0a1-20170104030214) and also on the Nightly specified by the reporter and haven't managed to reproduce it.
Following the User Story, when opening the provided url, after scrolling to the iframe between the mentioned sections (see attachment 8823906 [details]), when hovering and scrolling in the iframe with the scrollable area, the area is scrolled down as expected.

Considering the fact that I cannot reproduce this and the fact that the reporter's account has been disabled, I will mark this as Resolved-Worksforme.

If anyone can still reproduce it, feel free to reopen the issue and provide more information.