It is a contingency. A prolly-fill of sorts. Once support for IE8 and relics such as attachEvent are gone, then, a lot of the pain can be eased. You won’t find JQuery here. You may discover that this page is based off of a standard JQuery for desktop tutorial called Nike Better World - ‘Behind the scenes’ taught at Smashing Magazine.
You can see the project for yourself and decide whether it is really for you or not.
Three seconds. That is the threshhold limit of time at which point a common website visitor decides to pull stakes and bail if your content is not fully loaded or interactive. I have always maintained that JQuery (with CDN or otherwise) increases the likelihood of another fleeing customer.
This was constructed in 2011 or thereabouts. Fortunately, today in 2017 I can strip any references to documentElement.attachEvent type of code. Most importantly, I culled for the most part code that depended on browser sniffing even when it applied to progressive enhancement-friendly devices. Today, on the other hand, even if it is anti-pattern, I have limited browser sniffing to graceful degradation-dependent devices such as the case with an iOS4 device which will never respond to window.matchMedia. And, I have thrown in some additional media-queries that are based on (max-width) values as opposed to (max-device-width). To express it in another way, viewport dimensions are more inclusive than screen dimensions.
I have no time at the present moment, but when I do one day maybe I will revisit this page with new image assets that do not choke when it is time for them to be minified. Until then I will only pipe them from one place to the other. And, I am supporting the last 6 versions because of my partiality for iOS4 as I have explained. Otherwise, I would have been happy with the normal last 2 versions that I normally apply.
If I were to refer to this project as parallax for mobile-devices, that would be a fallacy on my part. I added the mobile portion years after I had originally composed the original desktop version for each w3c-compliant browsers and IE8 at the time. Good timing helped, too. I saw Paul Irish in a youtube video and he obliquely referred to a writeup of his own professing the benefits of css translations. Thank you, Paul -- I learned a lot on the subject.
If a browser is capable and expected to pick a media extension it will do so on its own. When audio and video are served, it is best to serve only what is necessary so that any other impertinent items are not stored in browser cache. This is my motive for, first, serving a single media extension, then, to apply the element in phases for only one reflow in contrast to multiple reflows courtesy of the createDocumentFragment directive. I learned this from Nick Zakas on youtube. Thanks, dude! :)
As if you cannot tell, indeed, I am a One Piece fan! But I had not always imagined the parallax project to be centered around the two characters you see. When, I imagined parallax, I imagined something similar to the 1980s video for "Silent Lucidity" by Queensryche. I was always impressed by the drummers set up in that video, thus, I will always associate those drums especially with a parallax effect figured prominently against a dark background. Today, however, the content contained within the project is based on an actual love-letter I received when I was 16 years old from my girlfriend who would like to joke around. This was before the internet and e-mail between the years of 1985 and 1989.