Webkit class-based effects still persist in doing nothing.

refer to ticket:4324 and ticket:3112 for more information and evidence of this bug.

Sorry for starting a new ticket. I wanted to reopen #3112 but don't have the privs.

One of two things is wrong:

1. The demo pages for effects have not been updated to the newest and fixed version, or

2. The problem has not been fixed.

I just discovered this bug when trying out all of the demos. I am using:

   Google Chrome 4.0.249.78 (Official Build 36714) unknown
   WebKit        532.5 
   V8            1.3.18.19

This is not a minor problem, in terms of impact. Chrome is very close to releasing stable, non-beta versions for Mac and Linux. Safari and Chrome are both available for Windows. Chrome is marketing HARD. Most Mac users have Safari has their default browser, maybe 30-40% (at most) use Firefox. 100% of iPhone, iPod touch, and, very soon, iPad users are on a WebKit browser.

Since the method doesn't effect non-class related effects, I would be very eager to not only investigate this at the jqueryui level, but on the jquery core level. If WebKit handles classes differently, this could effect many add-ons and future features of the core.

Letting this slip by can only discourage web-developers from jquery, give end-users a bad association with sites with a certain "look and feel", and, worst of all, prevents jquery from being the number one js framework for iPhone web-application developers.

I would much rather use jquery than Cocoa Touch and C#. I would much rather make web-apps that can shift seamlessly from desktop to android to iphone. But with this problem having been reported almost two years ago with only workarounds and incomplete fixes offered, I truly hesitate when considering jquery for projects that I know will have heavy Mac/iPhone visits. Not because a couple of simple effects don't work, but because of the unshakable concern that this indicates issues not yet noticed or uncovered.

I love jquery and jqueryui was my gateway to it. I don't particularly like Chrome or iPhones. But when I have to make the choice between a framework that I like and that works great in my preferred browser, and one that will work reliably for my users, I have to make a painful choice.

Sorry for the melodrama, can we just get this fixed?