Safari 4.0.2 fixes the crasher with LazyMouse
07/08/09 07:36 PM
The bug referenced in my previous
post has been fixed with the latest Safari
4.0.2 released today. Everyone who uses
LazyMouse should run Software Update and get the
newest Safari right away.
To recap, Safari 4.0 introduced a bug that would cause Safari to crash when it visited certain sites if some applications that use accessibility APIs were running. It was annoying that LazyMouse users were affected by this, but it was downright wrong that folks who use Apple’s VoiceOver also had this problem. It was even worse that Safari 4.0 came out the first day of WWDC, so everyone running LazyMouse who wanted to buy a new iPhone or MacBook Pro was bitten by this bug.
By the time I was able to identify the problem and report a bug to Apple’s radar bug tracker, apparently several other people had reported the same bug, and I received the cryptic “your bug is a duplicate” email from Apple. So I had no way of knowing if and when the bug would be fixed.
If you want to know what frustration is, try being the developer of a product that’s been broken by an Apple update. Although I had done my due diligence and I knew the problem wasn’t with my code, I still don’t like laying my problems off on someone else. For a while, I was getting a bug report every few hours, every one of them conscientious, some of them very long and thorough, reporting multiple sites that were affected by this and step by step instructions to reproduce the problem. All I could say was “Yes, I blogged about this the other day and I’ve told Apple. Here’s the link to my blog”.
It gets old fast.
But that doesn’t matter because Apple’s chosen, in their great wisdom, to see fit to fix the problem and so now I can tell people everything’s okay again. I’m happy.
I want to thank everyone who reported this bug to me. Although I couldn’t give you much help at the time, it’s nice to know I have such a conscientious, helpful user base.
Oh, and btw, if you excluded Safari in LazyMouse’s preference pane, you can un-exclude it after you upgrade to Safari 4.0.2.
To recap, Safari 4.0 introduced a bug that would cause Safari to crash when it visited certain sites if some applications that use accessibility APIs were running. It was annoying that LazyMouse users were affected by this, but it was downright wrong that folks who use Apple’s VoiceOver also had this problem. It was even worse that Safari 4.0 came out the first day of WWDC, so everyone running LazyMouse who wanted to buy a new iPhone or MacBook Pro was bitten by this bug.
By the time I was able to identify the problem and report a bug to Apple’s radar bug tracker, apparently several other people had reported the same bug, and I received the cryptic “your bug is a duplicate” email from Apple. So I had no way of knowing if and when the bug would be fixed.
If you want to know what frustration is, try being the developer of a product that’s been broken by an Apple update. Although I had done my due diligence and I knew the problem wasn’t with my code, I still don’t like laying my problems off on someone else. For a while, I was getting a bug report every few hours, every one of them conscientious, some of them very long and thorough, reporting multiple sites that were affected by this and step by step instructions to reproduce the problem. All I could say was “Yes, I blogged about this the other day and I’ve told Apple. Here’s the link to my blog”.
It gets old fast.
But that doesn’t matter because Apple’s chosen, in their great wisdom, to see fit to fix the problem and so now I can tell people everything’s okay again. I’m happy.
I want to thank everyone who reported this bug to me. Although I couldn’t give you much help at the time, it’s nice to know I have such a conscientious, helpful user base.
Oh, and btw, if you excluded Safari in LazyMouse’s preference pane, you can un-exclude it after you upgrade to Safari 4.0.2.