With the rise of flat design and it taking over the whole web, I’ve got this pet peeve with buttons that “wiggle” on hover. It’s becoming more and more common to have buttons where in one state they are flat and just have a nice background color, and in the hover state the background color changes and a border is added. Let’s have a look:
The CSS looks like this:
1 2 3 4 5 6 7 8 9 10 11 12 13
As you can see, hovering over the button causes it to wiggle, and the rest of the content below it to move. Not good enough.
The problem is caused because the button has no border on the regular state and a border is added on hover. The new border adds to the actual height and width of the button, making it wiggle and push all elements after it.1
I’ve seen CSS newbies solve this by adding a border with the same color to the normal state, which would work, but isn’t to my taste.
Whenever you want to have an element’s size not change due to inner changes such as borders, paddings, etc. you’re actually thinking about
So, just adding
box-sizing: border-box to our
.wiggle-button class gives us this new sexy button:
This is a cleaner solution, in my opinion, since it makes sure the border doesn’t cause size changes to the button. This magical attribute solves our problems in this case just like that, and is supported on all latest browsers2.
I hope you learned something new. Happy coding!
“Maintaining AngularJS feels like Cobol 🤷…”
You want to do AngularJS the right way.
Yet every blog post you see makes it look like your codebase is obsolete. Components? Lifecycle hooks? Controllers are dead?
It would be great to work on a modern codebase again, but who has weeks for a rewrite?
Well, you can get your app back in shape, without pushing back all your deadlines! Imagine, upgrading smoothly along your regular tasks, no longer deep in legacy.
Subscribe and get my free email course with steps for upgrading your AngularJS app to the latest 1.6 safely and without a rewrite.