> > On Tue, Aug 19, 2014 at 10:41 AM, Rick Byers <rbyers@chromium.org> wrote: > It's not just that it's heavy (talking with Jacob it appears we have about > the same hit testing costs as IE - roughly 2% of the 16ms frame budget). > There are certainly ways we could improve it, but at the cost of > additional complexity that could be spent on improving perf elsewhere. > Developers tell us that performance is the #1 reason they choose native > mobile platforms over the web (which is the #1 problem we're trying to > tackle). As such we're essentially unwilling to make any new design > choices which put the web at an inherent performance disadvantage relative > to Android and iOS native platforms. > So the assumption here is that developers will continue to choose native > over web because of the .3ms spent on hit testing during pointer movement? > I think that's really far fetched. I've met many many developers who prefer > Pointer Events over Touch Events, but less than a handful of developers who > prefer Touch Events over Pointer Events. I can't imagine that many > developers are concerned about the performance hit in this area over > developer ergonomics. > > 2014-08-20 21:05 GMT+03:00 Scott González <scott.gonzalez@gmail.com>: > On Tue, Aug 19, 2014 at 10:41 AM, Rick Byers <rbyers@chromium.org> wrote: > It's not just that it's heavy (talking with Jacob it appears we have about > the same hit testing costs as IE - roughly 2% of the 16ms frame budget). > There are certainly ways we could improve it, but at the cost of > additional complexity that could be spent on improving perf elsewhere. > Developers tell us that performance is the #1 reason they choose native > mobile platforms over the web (which is the #1 problem we're trying to > tackle). As such we're essentially unwilling to make any new design > choices which put the web at an inherent performance disadvantage relative > to Android and iOS native platforms. > So the assumption here is that developers will continue to choose native > over web because of the .3ms spent on hit testing during pointer movement? > I think that's really far fetched. I've met many many developers who prefer > Pointer Events over Touch Events, but less than a handful of developers who > prefer Touch Events over Pointer Events. I can't imagine that many > developers are concerned about the performance hit in this area over > developer ergonomics. > It would be good to have element.setPointerCapture({ trackBoundaries: false }); option. I understand position of Blink here, but PointerEvents are already here and they have this 3ms problem. I think it's absolutely should be fixed.Received on Wednesday, 20 August 2014 18:54:08 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:48:10 UTC