This crash only seems to occur on some graphics cards, and as far as I know, only on Windows, so I believe it has something to do with Chrome’s implementation of graphics acceleration.
Here’s a test page:
You should see a zooming, fading effect there. If you don’t see zooming, but you do see fading, then your browser doesn’t support CSS3 transform, transitions or both.
Safari doesn’t seem to have this problem.
If you experience a crash, it might be helpful for development folks to know which graphics card you’re using.
I’ve been doing a bunch of development work with CakePHP lately and have gotten to the point where I’m in a position to submit a few bug fixes and improvements back to the project. One small improvement has already been accepted, so that’s a great start! Working with Oracle, PHP, CentOS, and CakePHP has been an… interesting experience, so I’m hoping to get some information together about that process and make it a little easier for others in the future.
In other areas, I’ve been trying out Sass, Compass, and blueprint, with exciting results. If you wish for CSS to be more pragmatic and structured, these tools are for you. I’m particularly interested in the potential of very experimental CSS3 implementations, like transform and transition. Makes the web feel modern all over again.
When asked to support IE6, I would do it, but I’d do it like this. I actually rather like the idea behind the Universal IE6 CSS project, in that it still aims to provide a usable and clearly presented version of your site, substituting only CSS, but lets those users know they’re getting a much reduced experience. If they’re on the Internet, why haven’t they hopped on the future train yet? Come on people, get with the program. The fact that projects like this have to exist is pretty crazy, but now that we’re in this mess, I’m glad it does.
Further to the previous post about the Bombcast backdrop, Pepsi has been spotted getting in on the act!
However, it turns out this is not as much of a conspiracy as originally suspected. Ryan Davis has come out on Twitter saying that this is licensed artwork.
to be clear, no one’s ripping off anyone. That art is licensed, it’s just coincidental that GB and Pepsi’s agency both used it.
Consider the case closed. For now.
I’m sure all the Wave puns have already been made, and I’m not about to further muddy that particular pool. Google Wave is at least deserving of some attention, having just played around with the preview for a couple days now. It at least meets the original idea of being a good evolution of e-mail, with everything being conversation based as opposed to discrete individual messages that steadily grow in size as reply text is copied each time. Like some kind of out-of-control text-sponge being passed around, e-mails often reached the point where they rarely, if ever, related to the original message and became a form of delayed IM system. That’s an oxymoron, I know, but the advantage e-mails always had over IM was that they were not tied to one particular system or application.
Google Wave addresses the e-mail issue while introducing the very same IM issues. It is currently a closed system, and while the help topics do say the development team hope to implement traditional e-mail support in the future, I wonder how well that can work with the dynamic functions of Google Wave. Either Wave sends out periodic updates to “e-mail subscribers” of a particular Wave, or the Wave itself is limited due to the presence of e-mail participants. I’m sure the developers have thought about all this, though I’d still like to see what they come up with.
Besides the lack of backwards-compatibility with any existing system, the features of Google Wave do seem pretty exciting, as long as all your friends also have an account.