HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
cubiq
iscroll
JavaScript2011–2015
cubiq / iscroll · Archived

iscroll

Smooth scrolling for the web

4Distinct people
4Mentions
0Explicit recommenders
12.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Smooth scrolling for the web

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year4 dated mentions

Observed mentions: 2011-03-22 22:45:11 UTC to 2015-02-21 16:30:12 UTC.

0122011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20112012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC202
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC000
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC000
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101

What Hacker News says

4 sources
My GitHub search skills aren't the best, but here are some of the nicer ones I've found: Dynamic Physics Interactions for the Mobile Web: https://github.com/luster-io/impulse Facebook and Path style side menus: https://github.com/jakiestfu/Snap.js/ Smooth scrolling: https://github.com/cubiq/iscroll Add to home screen call-out for mobile devices: https://github.com/cubiq/add-to-homescreen Cross-browser usage of the JavaScript Fullscreen API: https://github.com/sindresorhus/screenfull.js/ Anybody know of any more?
In Statements about the Mobile Web
Tell me about it. If you've ever used iScroll (amazing library btw https://github.com/cubiq/iscroll) to get iPad scrolling support you'll see how deep the rabbit hole goes. I initially used it for 2013.artsy.net (source code: https://github.com/artsy/artsy-2013) and had to eventually decide to toggle it on only for iPad b/c there were too many edge cases in the browser. But I digress. Thanks for pointing this out, hopefully we'll eventually smooth over the quirks to a reasonable degree. Logged the bug for now: https://github.com/artsy/scroll-frame/issues/12
In Retain Scroll Position in Infinite Scroll
I don't want to pick too much on this project since it's in very early development, but this repeats a mistake that's also found in more mature libraries like iscroll.js: https://github.com/cubiq/iscroll The problem is that it uses CSS that works only in WebKit, but does not fall back gracefully in any other browser. It depends on CSS3 2D Transforms. Because the 2D Transforms spec is not yet a Candidate Recommendation, browser vendors currently implement it with vendor prefixes in case the spec changes before it's finalized. 2D Transforms are implemented in recent versions of IE (-ms-transform), Opera (-o-transform), Gecko (-moz-transform), and WebKit (-webkit-transform). However, the library uses only -webkit-transform. That wouldn't be so bad, except that it does this in a way that potentially breaks the page in other browsers. For
Read the rest
example, mobile Firefox supports overflow scrolling without any need for libraries. In the latest nightly builds of mobile Firefox 6 (which support touch events), adding iscroll.js to your page will actually break scrollable elements that work fine without the library. The solution is two-fold: (1) If you are using vendor-prefixed APIs you can easily support more implementations, and (2) do feature detection to fail gracefully on implementations that you don't support. And yes, I plan to submit patches to these projects to address these problems. (disclosure: I am a mobile Firefox developer)
In Scrollability

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.