News for hackers. Stuff that matters.

A comment on Intent to Implement: Pointer Events in Chrome. Parent comment

Re:Intent to Implement: Pointer Events in Chrome by o_____________o on Wednesday March 25, 2015 @01:53PM (#9264619)
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.

[ Parent | on HN ]
Re:Intent to Implement: Pointer Events in Chrome by acdha on Wednesday March 25, 2015 @02:55PM (#9265125)
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
[ Parent | on HN ]
Re:Intent to Implement: Pointer Events in Chrome by dmethvin on Wednesday March 25, 2015 @08:19PM (#9266989)
Here are some I'm aware of:

https://github.com/jquery/sizzle/issues/290

https://github.com/jashkenas/underscore/issues/2081

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.

[ Parent | on HN ]