The Tree Slider
Those of you running recent versions of Safari, Chrome, or Firefox 4 may have noticed some changes to tree browsing on GitHub. The new HTML5 History API (which really has…
Those of you running recent versions of Safari, Chrome, or Firefox 4 may have noticed some changes to tree browsing on GitHub.
The new HTML5 History API (which really has nothing to do with HTML — it’s a JavaScript API) allows us to manage the URL changes while CSS3 transitions handle the sliding. Permalinks are always maintained, your back button works as expected, and it’s much faster than waiting for a full page load.
Basically we intercept your click, call pushState() to change the browser’s URL, load in data with Ajax, then slide over to it.
When you hit the back button, an onpopstate handler is fired after the URL changes, making it easy to send you “back”.
Want more? Check out the HTML History API Demo and MDC’s Manipulating the browser history documentation. Facebook has blogged about their use of this stuff, and Flickr has been doing it for months on their lightbox view.
There’s also some hot replaceState() action over on our new Features page and the Pull Requests dashboard.
We’re still getting all the kinks out of the Tree Slider, but we hope you like it!
Written by
Related posts
GitHub Availability Report: October 2025
In October, we experienced four incidents that resulted in degraded performance across GitHub services.
TypeScript, Python, and the AI feedback loop changing software development
An interview with the leader of GitHub Next, Idan Gazit, on TypeScript, Python, and what comes next.
What 986 million code pushes say about the developer workflow in 2025
Nearly a billion commits later, the way we ship code has changed for good. Here’s what the 2025 Octoverse data says about how devs really work now.