Webkit/Safari 4.0.2 still crashing?
According to the article linked from this topic, Webkit nightly builds and Safari 4.0.2 fix the accessibility crash. But I'm seeing both of them crash when Fantasktik is enabled. Worse, although Fantasktik will exclude Safari via the preference, it won't exclude Webkit, or other Webkit-based apps like Fluid.
Do you have a radar # for Apple? Are you able to reproduce this? I can get it to happen whenever Fantasktik's running by:
1. Go to Facebook
2. Find one of the "write a comment" textareas in your feed (e.g. someone's wall post, photo, etc.)
3. Type "a" <cr> <cr> "b"
Before you can type the "b", Safari crashes.
</cr></cr>
Do you have a radar # for Apple? Are you able to reproduce this? I can get it to happen whenever Fantasktik's running by:
1. Go to Facebook
2. Find one of the "write a comment" textareas in your feed (e.g. someone's wall post, photo, etc.)
3. Type "a" <cr> <cr> "b"
Before you can type the "b", Safari crashes.
</cr></cr>
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has acknowledged this problem.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?I noticed that Safari 4.0.2 was working now with the Apple Store but I didn't check with other websites.
Fantasktik installs a standard accessibility listener on the applications, so I think there is still a bug in Safari/Webkit.
Are you able to reproduce it by turning off Fantasktik and enabling VoiceOver? -
Inappropriate?ok I've just checked and it's crashing with VoiceOver so it's still a Safari bug.
Unfortunately there's not much I can do about it. Apple needs to fix it. -
Any chance of a way to ignore Webkit/Fluid/etc. the way you ignore Safari? I tried the top "filter" list, but it didn't seem to prevent the bug. -
Inappropriate?Also: could you give me the original radar # that Apple assigned? I want to report this, but I want to make sure they know this isn't the bug they already fixed.
-
Inappropriate?The radar # for the initial issue is 6888669
Loading Profile...



EMPLOYEE