somewhere to talk about random ideas and projects like everyone else

stuff by antimatter15

Hi. I’m Kevin Kwok, and I’m currently a junior at MIT, and this is my obligatory online presence or whatever.

This is my little corner of the internet, where I talk about random projects and ideas and stuff.

If you want to contact me or read obnoxiously nostalgic autobiographical trivia, check out the about section.


Archive

Tags

3D actionscript ajax ajax animator api apple arduino art awesome blog browser bugfix canvas change chrome code color colors css design doge elitist evil experiment export extension ExtJS fast features firefox flash format function future GAE github google google code google wave graphics hacking hardware hosting html5 idea image internet exploder ipad javascript json library light lines linux login magical meta microsoft microwave mirror mit multitouch new nostalgia ocr offline old onlypaths pi progress prototype python raphael release rewrite school security shiny ShinyTouch simple site small speed SVG touch update upload user interface vector vectoreditor version video vision vp8 vX JS wave webcam wikify wikipedia wordpress

The Forward Button 25 June 2010

Selection_006

Taken from the chromium site, which is really cool itself.
I would dare say that one of the least useful buttons on my browser has to be the Forward button. It’s the analogue for the far more used back button, but most of the time, people progress forward, not backward (obviously a pretty good thing). There’s still a huge bit of potential for this underused button. I have a mouse with buttons on the left side for navigating forward and back, It’s really quite nice (though the triple-click button makes me develop a tendency to click randomly when reading, which makes those sites with the double-click lookup very annoying).

One of the most horrible developments in usability has been Pagination, because someone thought it would be a great idea to split everything into annoying separate pages. Sure it was a way to get around a technical issue of browser reflow while progressively rendering and bandwidth usage. But it set a nasty precedent for the future of web-interaction.

Now we have to live with it.

So I was thinking, is there any way to use my side buttons in Javascript? I quickly prototyped a demo but to my dismay, clicks only triggered with a .button of 0, 1 or 2. Then I realized that I could programatically alter history and detect hash changes. So then came another prototype which worked by setting the URL to “#Math.random()” and then doing a history.go(-1), hooking onto window.onhashchange to see when something changed. Then I discovered the new HTML5 history.pushState() and onpopstate events and switched accordingly.

Now, that it’s possible to trick the browser into populating the future of history. How do you decide what the user is probably going to next? The great thing is that if we guess wrong, it doesn’t really matter, anything is still better than a non-functional forward button.

So how do you predict where the user wants to go next? In most paginated systems, on the top and/or bottom of a post is a series of links [1] [2] [3] [4]. The current page is usually grayed out and unclickable. This makes it pretty easy to detect, just iterate each link by node order, parseInt the innerText and see if there’s a single-number jump in the middle, offset it by one and then you get the next page in order.

I actually wrote this such a long time ago that I basically forgot where the extension is and after using it, I’ve disabled it myself because chrome seems to have a few nasty bugs that cause it to crash (tabs at least) quite frequently when it’s enabled. But here it is.


« Archives