Implement infinite scroll on dashboards to fix account switcher closing

[paulmolluzzo]

This is an alternative to PR #25 that also fixes Issue #19, just in a different way.

The more() function is gone, and instead there's an infinite scroll on the dashboard. It mashes the button from one page height away, so you shouldn't see the "More" button even with fast scrolling.

Also, this improves the isDashboard definition, catching ~/dashboard and organization dashboards too.

Closes #25
Fixes #19

[hkdobrev]

📝 smash perhaps?

[sindresorhus]

👍

[sindresorhus]

Good idea!

[sindresorhus]

Just a follow-up question, would it be possible to always have the next page loaded when you scroll down? So you wouldn't have to see the loading indicator and wait.

[paulmolluzzo]

I suppose you could just remove the scroll distance if test on line 70:

if (wScroll > (btnOffset - wHeight)) {
    btn.click();
}

Leave only the btn.click() and it'll start (s)mashing that button on every scroll. It's possible that there'll be a performance hit, so I'd want to debounce/throttle it, but it's up to you.

[paulmolluzzo]

If you want to do that LMK and I'll make a new PR. Keep in mind that cmd+↓ is an immediate scroll to the botton and the button will show a loading gif as it makes the XHR to GH and then updates the DOM, so there's always some edge there (I think).

[sindresorhus]

@paulmolluzzo Hmm, not that important. Let's leave it like it is for now.