Less noise during development this way.

I needed to dig the reference from deeper in the structure. Not nice but
this works.

Far neater this way. Easier to use as well given you don't need to care
about the implementation...

Earlier this was one step too far so it worked only after two passes
(initial was skipped). Simp...

Obviously breaking changes, mostly internal, though.

Now it expects you to manage toggling on row level. This way the
rendering logic picks up the ch...

Not ideal but otherwise it would update the site even on canary
releases.

Toggling interface needs to change.

This fixes search when it runs out of results to show within the
viewport.

Otherwise you might get weird behavior by the looks of it.

It would be easy to make it possible to pass the initial scroll state
through a prop if needed.

This likely needs to change. The visibility state should go within the
row data as otherwise the...

This uses the same resolver as the table. The idea is that
`VirtualizedBody` accumulates all mea...

This needs to be shared between table and virtualized.

This is a breaking change but it's necessary to keep that interface
tidy. Esp. rowKey is needed ...

Still needs some work (folding!).

This is consistent with the rest of the APIs. Unfortunately this is a
breaking change.

Instead of removing measurement data, it's retained. The solution isn't
ideal, though. This need...

This fits the overall system (`compose`) better.

Cleaner this way.

Now routes are closer to content. Much neater this way.

Looks like Document iframes don't clean up correctly. Better solve this
by initializing drag and...

Better as a core utility.

It's better to provide this as an utility.

Now it passes `window` instead of `document`. It defaults to browser
`window` if you don't pass ...

Better this way.

This is needed for iframe tweaks. Still need to figure out how to deal
with resizing as that nee...

More flexible this way.

This revealed an issue at easy. Given it maintains styling through a
global stylesheet, it's not...

Now row rendering looks the way it should (padding updates).

Still need to improve virtualized algorithm so that it works better with
filtering. In that case...

Also made this to use the current resolution interface. Looks like it
was using the old scheme s...

This is handy for virtualization as row indices don't map to actual rows
there. Instead it's bet...

A little cleaner this way.

More logical this way.

The value shown at the UI isn't correct. This needs some tweaking.

These issues became apparent with a larger amount of data and scrolling.
Scrolling can lead to h...

Now the CSS classes for even/odd don't flicker anymore.

Just index * height. No more than that needed.

Dropped a redundant check and improved formatting.

This avoids a React warning.

Looks like the newest ESLint lints this better.

That can happen if startIndex is zero so better check.

Now this actually works. Still some debugging to do.

Still need to add math and rendering logic.

Now the naming is consistent.

This will deal with rendering extra rows for padding. Cleaner than
hacking around with data rows.

A little better now. Also re-enabled `Table` `shouldComponentUpdate`
given that seems valid.

St...

Still need to add padding to table beginning and figure out why
`BodyRow` `shouldComponentUpdate...

This way we can track heights per row index properly. The scheme will
fail with sorting and sear...

Still missing some bookkeeping, placeholder row to take space (scroll!),
and scrolling related l...

`onScroll` is going to need an extra hook as it needs force refresh for
the logic to work.

This still needs calculation to work but after that the first version
should more or less work. ...

Still missing scroll related logic. That's a hard part.

This actually needs some work at reactabular-table.
`shouldComponentUpdate` checks should become...

No sense in sorting that.

Also bummed some code out of the implementation and structured it better so
it's a little neater...