onScroll doesn't work in IE8

[zpao]

Here's an example: (no jsfiddle because that's broken in IE8)

http://playground.zpao.com/react/onscroll.html

[fabiomcosta]

I tried to fix this bug yesterday but had a bad time trying to find a fix for a similar cases.
I looked at current well maintained libraries and didn't find a way to make scroll bubble or capture it on IE8.
Seems like trying to fix it would be a waste of time and would make code much complex, for a browser that is slowly dying.
My suggestion is to point that out on the documentation.

http://www.quirksmode.org/dom/events/tests/scroll.html
http://dojotoolkit.org/reference-guide/1.9/dojo/on.html#event-delegation
http://api.jquery.com/on/#additional-notes

[zpao]

Seems like this isn't so easy. Let's do what @fabiomcosta says and document it.

[fabiomcosta]

@zpao do you think that we should do a console.warn everytime someone uses onScroll on any browser or would that be annoying? I would say it would be annoying but it would also be very frustrating to figure that it's a React limitation after some hours of debugging on IE8 (ugh!)

[petehunt]

+1 on the warning -- would be super helpful.

[petehunt]

reopening so we can add a warning

[cpojer]

Warning was added in f3e7745

[plievone]

Now that events are listened on demand, maybe the warning should be moved to ReactEventEmitter.listenTo method, where support is already checked?

[rakeshok]

It also prints the warning if you render on the server, its annoying :/

[sophiebits]

That's odd, I wouldn't expect that code to run at all when using server rendering.

[vmakhaev]

I see this warning when I'm doing TestUtils.renderIntoDocument with node-jsdom. Any chance to disable it?

[b2whats]

I also see this error when using ssr

[hammer65]

This is happening to me with JSDOM as well and in my case our team project standards aren't going to accommodate leaving these errors in the console when tests are run. How can I suppress or stub this out. It's not just obnoxious it is preventing me from getting my work merged in our project.

[anthonyhastings]

@vmakhaev / @hammer65 - I am now seeing this error after upgrading my version of Enzyme to 3.1.0. Did you find a way to suppress these warnings for JSDOM?

[gaearon]

If you're having problems please file a new issue.
Nobody actively reads old issues, and requests for help here will get lost.