Bug 220772 - Web Inspector: REGRESSION(?): four empty "webkit.org" style sheets are shown
Summary: Web Inspector: REGRESSION(?): four empty "webkit.org" style sheets are shown
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: WebKit Nightly Build
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2021-01-20 10:22 PST by Devin Rousso
Modified: 2021-03-08 15:55 PST (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Devin Rousso 2021-01-20 10:22:24 PST 
# STEPS TO REPRODUCE
1. inspect <https://webkit.org/>

# NOTES
all four resources show "An error occurred trying to load the resource".  The style sheets are not shown when reloading the page after Web Inspector is already opened.
Comment 1 Radar WebKit Bug Importer 2021-01-20 10:22:35 PST 
<rdar://problem/73409796>
Comment 2 Patrick Angle 2021-01-20 11:08:55 PST 
I'm not able to reproduce this issue inspecting <webkit.org> on top of tree. Are there any additional reproduction steps? All four style sheets are showing their content, as well as all the expected headers both when loading from the cache as well as when loading over the network.
Comment 3 Devin Rousso 2021-01-20 16:49:53 PST 
I am not able to reproduce this in ToT, but I am able to reproduce this in STP 118+
Comment 4 Joseph Pecoraro 2021-01-25 11:44:51 PST 
(In reply to Devin Rousso from comment #3)
> I am not able to reproduce this in ToT, but I am able to reproduce this in
> STP 118+

Perhaps this is a release build issue with minified sources?
Comment 5 Patrick Angle 2021-03-08 14:30:44 PST 
I'm no longer able to reproduce this with System Safari, Safari Technology Preview 121, or ToT with minified sources. @Devin Can you confirm that you can no longer reproduce the issue?
Comment 6 Patrick Angle 2021-03-08 15:55:14 PST 
Devin and I talked, and there is now a way to reproduce this issue. Follow the steps from the initial report, but also make sure you have the Wipr (https://apps.apple.com/us/app/wipr/id1320666476?mt=12) content blocker extension installed.