CSShake: Some CSS Classes to shake your DOM
elrumordelaluz.github.io
elrumordelaluz.github.io
edit: Sidenote: I've stumbled upon an interesting Google Easter egg: https://www.google.co.in/search?q=blink+tag
Edit: I just realized, it's a vertical carrousel, in its full glory with almost invisible next and prev buttons, and its 8x8 pixel navigation buttons. This summarizes pretty much everything that's wrong with modern web design.
No it does not. It's MUCH better experience. Maybe firefox has a crappy implementation of it? I've been using smooth scroll for as long as I can remember (except on linux where it was slow) and it is really that much better. Jumping randomly and trying to figure out where you were? Better than naturally move the view? Really?
That being said, I agree with you that this site is broken. I can't use pg-up/down or home/end, yet the site acts as if it were a regular vertical page.
However, I can think of some great uses for it:
- Very similar to iPhone's "delete", which most people are familiar with. It means "Hey, I can be dragged"
- Could be good for refusing to do an action. Apple shakes the login box when you use the wrong password.
- A tiny notification icon could shake every few seconds to get someone's attention.
- Some logos (a car?) could look cool shaking for a second or two (either right away, or on hover).
- In tutorials, to show a button/element that the tutorial is talking about
A checkbox must be checked before submitting the form? Shake the ckeckbox when the user clicks submit.
Log-in failed? shake the log-in form.
And instead of keeping our mouths shut, or better yet, say thanks, we go on about this being a bad idea. Talk of ungrateful.
Open source projects don't need a higher, mightier directive. He/she has put his work out there. Show some respect.
We can't just venerate something because it's been "given to the people" - we need to give OS just as much critical treatment as closed source. Otherwise, the community becomes a sycophantic collection of yes men, and those outside of it can't treat the products in the movement seriously in comparison to commercial offerings.
Criticism in its constructive form is vital for improvement, regardless of the intentions of someone putting something out there.
Nowadays, when I release any code I tend to write a description of said code to illustrate how I intend it to be used. If I'm writing something that I believe shouldn't be used on a production project I will explicitly state this. I don't release a lot of code, but I've released a few snippets of untested, hacky code before that has found its way into production sites, and the last thing I want is for people to slate me just because I thought I'd show off what I had written.
This kind of thing happens all the time, almost monthly on Hacker News and Reddit. Everyone would probably be a lot happier if people were to add a basic disclaimer to their code to say "Hey, I've written this for a bit of fun. Don't use it on a user-facing site, okay?" to released code if they don't intend for it to be used on production sites by others. It may not be applicable in this case, but I reckon most cases where people bitch about how shitty some open source code or technique is would be solved if an author would explicitly state the use case for their code.
Decent manners towards other human beings aside, my main point is that a lot of the negative criticism we see towards released code and tools on communities like HN and Reddit would disappear if authors would explicitly state the intended use case for their work.
Are there any use cases where this might be practical? iOS has the app icons quaking in fear when you tap-hold on them, although the effect is somewhat different...
Someone else's CSS animation for reference http://jsfiddle.net/MWgnf/23/
(It appears to work only in Firefox.)
Of course, there is potential for abuse. But the same could be said for most of jQuery's animations or any other such library.
It shows attention to detail and finesse, you took one simple idea and went above and beyond making multiple implementations for different use cases, presented in the most exquisite and pleasant way.
Code and beauty. Great skills to have.
When someone makes a mistake, I like to pick it up and shake it in their face. This has a soothing effect.
And everyone wonders why I'm still using as my main browser one that doesn't support CSS animations... and I do have blink and marquee filtered out.
- It will be abused by ads, and annoying "CLICK HERE AND SUBSCRIBE TO MY SHITTY BLOG!" messages.
- If it ever gains popularity, all major pop-up/ad-block/no-script applications will add a couple lines to remove it.
«mucho more information» sounds really bad. Information in Spanish is Información, which has female gender. Thus, you should better write «mucha more information».
Just a linguistic tip: you mean gender, not genre. :)