Observations from a half-fried, half-Chinese, half-Australian American.

Recently, I’ve had the pleasure of building the UI for a client program using Webkit. Access to all the CSS3 features has been great as well as completely liberating from the constraints of IE compatibility.

WebKit offers another great feature: the -webkit-transition property to animate transitions between different style declarations. One obvious application is fading an element in and out which requires a CSS property which I’ve long since relegated to the pile of “nice, but not so applicable” properties: “visibility.”

here’s an example:
.module {
visibility: hidden;
opacity: 0;
-webkit-transition: opacity 0.2s ease-in;
}
.module.display {
visibility: visible;
opacity: 1;
}


Why not just use the display property? Because even if display is “none”, an absolutely positioned <div> will block click and other mouse events from being detected by elements below (in terms of z-index) the hidden <div>.

Well, I signed up for the Versions app beta and finally got it about a bit over a month ago. I installed it and then minutes later, I clicked it off, fired off an email to their feedback address and removed it from my dock, expecting never to use it again. You see, the problem was I couldn’t get it to work with my Site5 SVN setup. I received an email back from the beta team and now it’s working and back in my dock.

Read more