WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
220596
PCM: Output logs by default, including to Web Inspector
https://bugs.webkit.org/show_bug.cgi?id=220596
Summary
PCM: Output logs by default, including to Web Inspector
John Wilander
Reported
2021-01-13 11:21:14 PST
Logging for PCM should be readily available in Web Inspector and not require the experimental PCM Debug Mode.
Attachments
Patch
(15.60 KB, patch)
2021-01-13 11:31 PST
,
John Wilander
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1
2021-01-13 11:21:37 PST
<
rdar://problem/73159180
>
John Wilander
Comment 2
2021-01-13 11:31:13 PST
Created
attachment 417550
[details]
Patch
John Wilander
Comment 3
2021-01-13 13:15:09 PST
mac-debug-wk1 layout test failure unrelated. Looks flaky in history view. I pinged the bot watchers.
Brent Fulgham
Comment 4
2021-01-13 15:21:37 PST
Comment on
attachment 417550
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=417550&action=review
r=me
> Source/WebCore/loader/PrivateClickMeasurement.cpp:65 > + return makeUnexpected("[Private Click Measurement] Conversion was not accepted because the URL's protocol is not HTTPS or the URL contains one or more of username, password, query string, and fragment."_s);
Do we need to do any kind of feature check to decide whether to handle the attribution requests? Or does the flag only controlling emitting the report? After thinking about it, I think that makes good sense since a developer could test (and see this output in WebInspector) without actually triggering any conversion events.
John Wilander
Comment 5
2021-01-13 15:42:57 PST
(In reply to Brent Fulgham from
comment #4
)
> Comment on
attachment 417550
[details]
> Patch > > View in context: >
https://bugs.webkit.org/attachment.cgi?id=417550&action=review
> > r=me > > > Source/WebCore/loader/PrivateClickMeasurement.cpp:65 > > + return makeUnexpected("[Private Click Measurement] Conversion was not accepted because the URL's protocol is not HTTPS or the URL contains one or more of username, password, query string, and fragment."_s); > > Do we need to do any kind of feature check to decide whether to handle the > attribution requests? Or does the flag only controlling emitting the report? > > After thinking about it, I think that makes good sense since a developer > could test (and see this output in WebInspector) without actually triggering > any conversion events.
Yes, I think that's right. Thanks for the review!
EWS
Comment 6
2021-01-13 16:10:12 PST
Committed
r271473
: <
https://trac.webkit.org/changeset/271473
> All reviewed patches have been landed. Closing bug and clearing flags on
attachment 417550
[details]
.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug