![]() However in the interim, let's also come up with a good general purpose solution so that it's easier for React users to handle this change. Let's figure out the best API for passive event handlers in React moving forward. ![]() Both teams are aligned in this goal, even if coordinating on a change like this could have been smoother.įorcing wheel events to be impassive would create additional breaking changes for React users, while undermining performance improvements on the platform. ![]() ![]() Much like React, Chrome is in a position to improve user experience across a broad base of users. Our metrics show that 75% of the wheel and mousewheel event listeners that are registered on root targets (window, document, or body) do not specify any values for the passive option and more than 98% of such listeners do not call preventDefault(). Our goal with this change is to reduce the time it takes to update the display after the user starts scrolling by wheel or touchpad without developers needing to change code. The Chrome team didn't do this in a vacuum, and took the time to research this thoroughly, as linked in the original issue description ( ): Sorry to hide your comment, but it doesn't help us come to a resolution and I want to keep this issue focused for others coming to the React issue board that might be confused.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |