4 ms·

pointer event madness. file selector crash. <option> crash. rem bugs. insane RAM usage. crash from RAM usage. crash from greedy CSS selectors. canplay event nev

pointer event madness. file selector crash. <option> crash. rem bugs. insane RAM usage. crash from RAM usage. crash from greedy CSS selectors. canplay event never fired on media. That's just from the last few weeks. Can't imagine anyone who has built a moderately sized web app would think Safari's biggest problem is just being a little slow on the uptake. In better news, wkwebview is a big improvement. Hopefully it's a sign of things to come.

acdha 12y ago
Do you have bug reports for any of those? That RAM usage in particular suggests that the problems are more likely either specific to your application or an extension
- dmethvin 12y ago
  Here are some I'm aware of: https://github.com/jquery/sizzle/issues/290 https://github.com/jquery/sizzle/issues/290 https://github.com/jashkenas/underscore/issues/2081 https://github.com/jashkenas/underscore/issues/2081 https://github.com/jquery/jquery/issues/2145 https://github.com/jquery/jquery/issues/2145 Webkit devs are aware of these and they have been fixed in Webkit core, but Apple doesn't provide any info about when the fixes may see the light of day.