[Webkit-unassigned] [Bug 250779] New: Web Inspector: ITPDebug does not write to terminal / console

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jan 18 12:09:30 PST 2023


https://bugs.webkit.org/show_bug.cgi?id=250779

            Bug ID: 250779
           Summary: Web Inspector:  ITPDebug does not write to terminal /
                    console
           Product: WebKit
           Version: Safari 16
          Hardware: Unspecified
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Web Inspector
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: cory at cunderwood.dev
                CC: inspector-bugzilla-changes at group.apple.com,
                    wilander at apple.com

Seen in Safari 16.2 (17614.3.7.1.7, 17614)

Description:  After enabling Debug mode, it does not appear that the debug mode is being engaged (grepping logs has no returns).  Thus I am unable to determine what, if any, modification to storage behavior may apply to a website I am developing or testing.

Steps to Reproduce:
After enabling 'Enable Intelligent Tracking Prevention Debug Mode' under the 'Develop' menu both of the following methods were attempted:

1:  Executing 'log stream -info | grep ITPDebug' from Terminal does not find any messages upon page loading / refreshing with the debug flag enabled, even for sites I know should alert to cookie expire truncation due to CNAME record usage or coming from a known tracker source.
2:  Using Console and searching for 'ITPDebug' with info messages enabled does not find any messages upon page loading / refreshing with the debug flag enabled, even for sites I know should alert to cookie expire truncation due to CNAME record usage or coming from a known tracker source.

Both methods used to work previously for determining which cookies may have shortened duration due to CNAME Cloaking abuse.

Additional Context:

I *do* get Web Inspector console debugging information - such as 'Applying cross-site tracking restrictions:' and 'About to remove data records for:'.  

I am aware of the changes from Third-Party CNAME Mitigation to Third Party Mitigation, but can't see a method that identifies when that would be applied with the 'ITPDebug' flag enabled, or via any representation within the JavaScript Console or Web Inspector more generally.   

I was also unable to find any relevant documentation update which would explain this shift in behavior, or what to use instead on webkit.org.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230118/76f93774/attachment.htm>


More information about the webkit-unassigned mailing list