Thanks for working on this!! :) On Tue, Sep 5, 2023 at 5:27 PM Yash Joshi <yashjoshim...@gmail.com> wrote:
> Just sharing an update. Tentative WPT Tests Added in CL : > https://chromium-review.googlesource.com/c/chromium/src/+/4659532. > Feature Implementation Behind RuntimeEnabled Flag CL: > https://chromium-review.googlesource.com/c/chromium/src/+/4812813 > Regards > On Tuesday, September 5, 2023 at 8:47:02 PM UTC+5:30 Yash Joshi wrote: > >> Contact emailsyashjo...@gmail.com >> >> Explainer >> https://docs.google.com/document/d/1ODMUQP9ua-0plxe0XhDds6aPCe_paZS6Cz1h1wdYiKU/edit >> >> SpecificationNone >> >> Summary >> >> This feature enhancement proposes the addition of a new field to the >> PerfomanceResourceTiming API which will expose the initiator information, >> allowing the creation of dependency trees from Real User Monitoring (RUM) >> data. This enhancement will greatly improve understanding of resource >> loading performance, enabling developers and RUM providers to optimize web >> apps for faster performance. >> >> >> Blink componentBlink>PerformanceAPIs>ResourceTiming >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EPerformanceAPIs%3EResourceTiming> >> >> Motivation >> >> Before Task Attribution API had landed there was no way to identify which >> JS is the initiator of other JS tasks. Developers thus needed to rely on >> costly runtime stack analysis or third-party tools for insights into >> resource loading. By leveraging Task Attribution, this project aims to >> pinpoint resource triggers, enabling early optimization and better resource >> management. Real User Monitoring (RUM) providers can benefit from accurate >> dependency trees, improving resource insights and optimization decisions. >> >> >> Initial public proposalhttps://github.com/w3c/resource-timing/issues/263 >> >> TAG reviewNone >> >> TAG review statusPending >> >> Risks >> >> >> Interoperability and Compatibility >> >> None >> >> >> *Gecko*: No signal >> >> *WebKit*: No signal >> >> *Web developers*: No signals >> >> *Other signals*: >> >> WebView application risks >> >> Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> >> None >> >> >> Debuggability >> >> None >> >> >> Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >> ?No >> >> Flag name on chrome://flagsNone >> >> Finch feature nameNone >> >> Non-finch justificationNone >> >> Requires code in //chrome?False >> >> Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1459950 >> >> Estimated milestones >> >> No milestones specified >> >> >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/6197847657021440 >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com/>. >> > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/90436bc2-bfd4-4680-bccc-c094bfa89d94n%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/90436bc2-bfd4-4680-bccc-c094bfa89d94n%40chromium.org?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfWeMau9t_fZdrj1j5qMNOCU5zD6e8q%3DvHOrJegg-4e0Zw%40mail.gmail.com.