Re:Swipe 2 is now live
by snsr on Monday March 11, 2013 @01:10PM
(#5358091)
I've found Swipe.js to be helpful in the past, looking forward to checking the new version out.
@bradbirdsall - Chrome canary calls out the mime type of swipe.js on the demo site. I don't think the HTML5 spec requires text/javascript though, so that's probably on Chrome.
Github serves pages from 'raw.github.com' with an "X-Content-Type-Options: nosniff" header, which specifically disallows browsers from trying to second-guess MIME types. FWIW, IE has supported this header for years, and Firefox is probably going to be adding it soon as well. So if you're serving your .js files with the wrong content type, they're going to break for more and more users as time goes on.
Re:Swipe 2 is now live
by Smudge on Monday March 11, 2013 @01:22PM
(#5358175)
I understand what you're describing to be their purpose. But the first thing I tried to do was click on them, and got confused/frustrated when they didn't do anything. This tells me their purpose is not in line with what I (and possibly others) expected.
Re:Swipe 2 is now live
by ericmsimons on Monday March 11, 2013 @02:02PM
(#5358514)
And what we're saying is that it's a bad demo. Demos are supposed to impress you enough to want to use the real thing. Your demo confused me and (apparently) a handful of other folks.
Instead of literally laughing off feedback and pretending there aren't any problems with your site, you may want to think a bit more critically about the presentation of your javascript plugin.
@bradbirdsall - Chrome canary calls out the mime type of swipe.js on the demo site. I don't think the HTML5 spec requires text/javascript though, so that's probably on Chrome.
Github serves pages from 'raw.github.com' with an "X-Content-Type-Options: nosniff" header, which specifically disallows browsers from trying to second-guess MIME types. FWIW, IE has supported this header for years, and Firefox is probably going to be adding it soon as well. So if you're serving your .js files with the wrong content type, they're going to break for more and more users as time goes on.
But in addition it should generally do what users expect. If the dots aren't clickable, why are they there?
Instead of literally laughing off feedback and pretending there aren't any problems with your site, you may want to think a bit more critically about the presentation of your javascript plugin.
If you're on a desktop, you're basically just sitting there watching it autoplay.