Summary: | Web Inspector: Native frames when refreshing page during timeline recording even though frames aren't native | ||
---|---|---|---|
Product: | WebKit | Reporter: | Saam Barati <saam> |
Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW --- | ||
Severity: | Normal | CC: | graouts, inspector-bugzilla-changes, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Local Build | ||
Hardware: | All | ||
OS: | All |
Description
Saam Barati
2016-06-05 22:18:24 PDT
Web give any call frame that doesn't have a source code location a "Native" appearance. We should see if we aren't getting a location, or maybe we get a location but it no longer makes sense. My bet is the location has a script identifier, but we clear the scripts when the page navigates. (In reply to comment #2) > Web give any call frame that doesn't have a source code location a "Native" > appearance. We should see if we aren't getting a location, or maybe we get a > location but it no longer makes sense. My bet is the location has a script > identifier, but we clear the scripts when the page navigates. Makes sense. As Joe says, in general we don't have source for old pages. We might want to flag these differently in the UI to have a non-native appearance but show we don't have source location anymore. |