Remove Mobile Firefox Button Gradient
If you have an Android device, you've gotta check out Firefox for Android. It's an outstanding mobile browser -- it has been very well received and you can even install apps from the Firefox Marketplace from within this awesome browser. One usability practice implemented by Firefox for Android is a gradient shade on all button elements. While I appreciate the idea, I don't necessarily want this added to elements which I want to look a very specific way. Removing this gradient effect is simple:
/* Cancels out Firefox Mobile's gradient background */
button {
background-image: none;
}
Before you jump on Mozilla for this practice, WebKit-based browsers do something very similar. Preventing this effect is also very simple so if you want to remove this gradient, use the code above and you're on your way!
![Vibration API]()
Many of the new APIs provided to us by browser vendors are more targeted toward the mobile user than the desktop user. One of those simple APIs the Vibration API. The Vibration API allows developers to direct the device, using JavaScript, to vibrate in...
![I’m an Impostor]()
This is the hardest thing I've ever had to write, much less admit to myself. I've written resignation letters from jobs I've loved, I've ended relationships, I've failed at a host of tasks, and let myself down in my life. All of those feelings were very...
![CSS pointer-events]()
The responsibilities taken on by CSS seems to be increasingly blurring with JavaScript. Consider the -webkit-touch-callout CSS property, which prevents iOS's link dialog menu when you tap and hold a clickable element. The pointer-events property is even more JavaScript-like, preventing:
click actions from doing...
![Control Element Outline Position with outline-offset]()
I was recently working on a project which featured tables that were keyboard navigable so obviously using cell outlining via traditional tabIndex=0 and element outlines was a big part of allowing the user navigate quickly and intelligently. Unfortunately I ran into a Firefox 3.6 bug...
Works with
inputandtextareaelements too :)