Looks like this was regressed...
http://bugs.webkit.org/show_bug.cgi?id=14327 says that webcore was changed to fix this problem.
Webkit revision 24276 contains the fix, so it would seem if by r89366 you were on revision 24781, you would have the fix in place.