Summary: | Propagate WebKit2Logging channels to the Web Process | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Simon Fraser (smfr) <simon.fraser> | ||||
Component: | New Bugs | Assignee: | Simon Fraser (smfr) <simon.fraser> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | commit-queue, simon.fraser, thorton, webkit-bug-importer | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Simon Fraser (smfr)
2017-12-06 17:40:59 PST
Created attachment 328666 [details]
Patch
Comment on attachment 328666 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=328666&action=review > Source/WebKit/ChangeLog:8 > + If you set WebKit2Logging, you want those channels active in both the UI process and I generally don’t, as that’s quite confusing. I guess I made the same comment when you implemented this for WebCore logging too. Comment on attachment 328666 [details] Patch Clearing flags on attachment: 328666 Committed r225655: <https://trac.webkit.org/changeset/225655> All reviewed patches have been landed. Closing bug. |