RAF measurement method is intended to include the complete render reflow process in the async time. However, current RAF measurement method will also result in additional async task is scheduled in the async time of the NewsSite-Next case. It's because _syncCallback and _asyncCallback timer are registered in separate RAFs. The Timer measurement method does not have this problem as it registers _syncCallback and _asyncCallback timer in the same setTimeout. Is it on purpose to include such async task in the async time?
RAF measurement method is intended to include the complete render reflow process in the async time. However, current RAF measurement method will also result in additional async task is scheduled in the async time of the NewsSite-Next case. It's because _syncCallback and _asyncCallback timer are registered in separate RAFs. The Timer measurement method does not have this problem as it registers _syncCallback and _asyncCallback timer in the same setTimeout. Is it on purpose to include such async task in the async time?
A quick hack to verify the score impact: