table.body onScroll action is fired when table is first rendered with occlusion

[lougreenwood]

The onScroll action is fired when the table has occlusion rendering enabled.

This has the effect of always return scroll position of 0 on table load. For us, this causes problems because it overwrites any previously stored scroll position (@onScroll={{action (mut scrollPosition)}}).

If occlusion is disabled, the feature works as expected.

[alexander-alvarez]

Thanks for bringing this up! Categorized it so we can investigate it further