71–75 of 75 posts
Awesome. But, shouldn't it be going from first commit to latest commit? Like telling the story of the project. Edit: Found the repo[0] in the page source. [0] https://github.com/artemave/StarLogs
even if not, it'd be pretty sweet if there was an option to do so.
There's small problem on how browsers respond, when we change the hash#parameter in the URL and hit ENTER in the sites where DOM is manipulated using AJAX depending on hash-value, like in this site. It doesn't get updated until we hit ENTER for second time in Chrome, reload in Firefox. I also have a similar site that manipulates DOM depending on hash value. If you are on instamovi.com/#bourne with bourne movies liste…
Earlier quoted context omitted.
Nice, but please consider switching to HTML5 history (pushState). It's just as easy and a lot cleaner. Especially that you can use popstate to let people switch the URL. It's amazing anyway.
If he were to use pushState for this, wouldn't he need a .htaccess (or other means) to point all requests to index.html? Meaning it's not just as easy?
This is very cool. I also just noticed a neat quirk - if you switch tabs (I'm on chrome) the animations pause but the timer to show the text keeps ticking. So all the text bunches up at the bottom until you switch back at which point the text blob starts to fade out all together. The page visibility api: http://www.w3.org/TR/2011/WD-page-visibility-20110602/ might be able to help with that.
For example, have a single, explicit 'scroll position' or 'time' variable (they're equivalent in this case), increment it on a timer, and insert new text when (time mod N) rolls over.