| Summary: | WIP: Maintain a stack of executing scripts to attribute webpage execution events | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Umar Iqbal <uiqbal> | ||||||
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> | ||||||
| Status: | NEW --- | ||||||||
| Severity: | Normal | CC: | bfulgham, cdumez, esprehn+autocc, ews-watchlist, japhet, kangil.han, katherine_cheney, keith_miller, mark.lam, msaboff, saam, tzagallo, uiqbal, wilander | ||||||
| Priority: | P2 | ||||||||
| Version: | WebKit Nightly Build | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Attachments: |
|
||||||||
|
Description
Umar Iqbal
2020-07-02 12:02:43 PDT
Created attachment 403385 [details]
Patch
We currently plan to capture classic script execution. Including their callbacks, eval/Function, and promises. This is in no way trying to capture all types (WASM etc) of scripts executing in a Document. I believe, you also won't be capturing transitive calls with this. I.e. if frame A calls a function exposed by frame B, which then calls into the DOM, you'll only see frame A. Not sure if that matters for now, though. Created attachment 403604 [details]
Patch
|