Bug 228555
| Summary: | Web Inspector: [Cocoa] Reintroduce strategic logging in RemoteInspectorCocoa that doesn't log to `stderr` | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Patrick Angle <pangle> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | inspector-bugzilla-changes, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | 228303 | ||
| Bug Blocks: | |||
Patrick Angle
r278413 added some additional logging to help diagnose issues with remote inspection. r280370 removed that logging because it occurred on `stderr`, which confused some clients of JavaScriptCore which relied on a clean `stderr` output to determine success, leading to compatibility issues with existing applications. We should reintroduce this logging using `os_log` to bypass `stderr` and log straight to the system log stream.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/81222691>