Bug 132386
| Summary: | Web Inspector: differentiate callback argument conventions by invoking commands differently | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Brian Burg <burg> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | bburg, graouts, inspector-bugzilla-changes, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Brian Burg
Right now there's one place where the code sets a magical .expectsResultObject on the callback passed to a backend command invocation.
I think we should disambiguate this by adding a different method (like .invoke or .promise) rather than using a magic property.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/16770631>
Blaze Burg
This is nowadays auto-detected based on the type of the last argument. Closing.