1181658 - Descendant elements become non-interactable after scrolling container passes a certain point.

Status: UNCONFIRMED

(Core :: DOM: UI Events & Focus Handling, defect)

Description

[jelbourn]

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36

Steps to reproduce:

Here is a JsBin that contains a reproduction of the issue: http://jsbin.com/zucado/edit?html,js,output

The bin contains a static snapshot of a situation that was encountered with a virtual scrolling implementation.

The idea is that there is a very, very large scrolling container, `.md-virtual-repeat-scroller`. The size of the container is determined by the size of `.md-virtual-repeat-sizer`, and the (arbitrary) content actually being shown on the screen is inside of `.md-virtual-repeat-offsetter`, which uses translateY to position visible content. 

(in the real code there is handling to adding and remove content and update the translateY as the scroller is scrolled, but this is not necessary here to reproduce the bug).


Actual results:

Once the scrollTop of the `.md-virtual-repeat-scroller` reaches a certain value (I found this to be 2096899), the elements inside of `.md-virtual-repeat-offsetter` can no longer be interacted with in any way, even though they are displayed in the correct position. 

The means that any events, such as click, have an event target of the `.md-virtual-repeat-offsetter` element. This problem even extends to the developer tools- trying to use "Inspect element" on one of the table cells again goes to the offsetter element.

I observed this behavior in Firefox 38 and 39, on Linux (Ubuntu), OSX, and Windows 8.


Expected results:

The elements inside of the offsetter should be interactable as normal. I confirmed this problem does not occur in any of the other browsers I had set up (Chrome, IE10, IE11, Mobile Safari, Chrome for Android)

Comment 1

[Michael Prentice]

I'm not clear on what the actual reproduction steps are? Is it just scrolling down with the mouse wheel until the dates no longer render at all? I must be missing something because I see the dates stop rendering when I scroll down on Chrome too.

Do I need to click on something? the blank space where a date should be? or something else?

I see that there is a lot of info logged to the console when clicking a date. But I'm not sure what to check to see if this is still an issue or not?