Bug 82278
| Summary: | WEB_TIMING related objects could be a supplement. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Hajime Morrita <morrita> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | abarth, burg, haraken, sergio |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Hajime Morrita
It could be a module or at least could be a supplementable and have its own directory.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Adam Barth
The problem with WEB_TIMING is that it needs to instrument many places in the code. It might not be worth making it a module...
Hajime Morrita
(In reply to comment #1)
> The problem with WEB_TIMING is that it needs to instrument many places in the code. It might not be worth making it a module...
Yeah... I'm thinking that we should have something like "instrument" component.
where inspector, chromium profiler, dtrace and this timing stuff live.