Interaction to Next Paint (INP) "subparts" : Ensuring Accurate INP Tracking in Chrome DevTools

[LIZA NANCY D'SOUZA]

Dear GSoC Team,

I hope you are doing well.

This is regarding the Chromium project 1: "Interaction to Next Paint (subparts)".

For my proposal, I am planning to improve the Interaction to Next Paint (INP) metric in Chromium by breaking it down into subparts. Now, this entire process involves modifying UKM reporting and Mojo IPC. So , I just wanted to clarify if there any specific guidelines or limitations regarding modifying Chrome’s telemetry and reporting structures that I should be aware of before doing anything like implementation?

I thought of using ChromeDev tools to first analyse the INP and responsiveness for different websites and record it . And I would appreciate if the GSoC team could tell me about any I would need to consider before doing this.I would also appreciate any insights on how to improve INP debugging accuracy.

Thank you,

Best Regards,

Liza Nancy D'Souza

[Sreeja Kamishetty]

Thank you Liza. Cc'ing project specific group.

[LIZA NANCY D'SOUZA]

Hello, Ms.Sreeja

Thank you for looping in the mentors and the team.

[Michal Mocny]

Hi Liza-- there is a description of the goals and steps outlined in the project proposal.  The entire project involves Chromium contributions, outside of DevTools.  It might be fun and useful to use DevTools to analyze INP but it would be not directly related to the work involved.

Cheers,

-Michal

[LIZA NANCY D'SOUZA]

Hello Mr. Michal ,

Thank you so much for the response, 

I've made the necessary adjustments to my proposal to align with the goals and I understood the real work in Chromium's source.

I really appreciate your guidance.

Best regards,
Liza Nancy D’Souza