WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
179233
Web Inspector: Network Table - Include a secure lock indicator in the domain column
https://bugs.webkit.org/show_bug.cgi?id=179233
Summary
Web Inspector: Network Table - Include a secure lock indicator in the domain ...
Joseph Pecoraro
Reported
2017-11-02 23:14:00 PDT
Include a secure lock indicator in the domain column This keeps the data in the table relatively compact but provides a useful indicator (was the request secure (https/wss) / insecure).
Attachments
[IMAGE] Before
(222.21 KB, image/png)
2017-11-02 23:14 PDT
,
Joseph Pecoraro
no flags
Details
[IMAGE] After
(225.25 KB, image/png)
2017-11-02 23:15 PDT
,
Joseph Pecoraro
no flags
Details
[IMAGE] Mixed Content
(200.32 KB, image/png)
2017-11-02 23:15 PDT
,
Joseph Pecoraro
no flags
Details
[PATCH] Proposed Fix
(3.14 KB, patch)
2017-11-02 23:15 PDT
,
Joseph Pecoraro
no flags
Details
Formatted Diff
Diff
[IMAGE] Edge Case - Failure on https
(186.79 KB, image/png)
2017-11-02 23:18 PDT
,
Joseph Pecoraro
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Joseph Pecoraro
Comment 1
2017-11-02 23:14:09 PDT
<
rdar://problem/34070883
>
Joseph Pecoraro
Comment 2
2017-11-02 23:14:57 PDT
Created
attachment 325860
[details]
[IMAGE] Before
Joseph Pecoraro
Comment 3
2017-11-02 23:15:07 PDT
Created
attachment 325861
[details]
[IMAGE] After
Joseph Pecoraro
Comment 4
2017-11-02 23:15:20 PDT
Created
attachment 325862
[details]
[IMAGE] Mixed Content
Joseph Pecoraro
Comment 5
2017-11-02 23:15:34 PDT
Created
attachment 325863
[details]
[PATCH] Proposed Fix
Joseph Pecoraro
Comment 6
2017-11-02 23:18:47 PDT
Created
attachment 325864
[details]
[IMAGE] Edge Case - Failure on https Adding an image for a failure to show that the lock icon is still gray and not red. I think a red lock would be bad, since it might indicate something else. I do think we will might eventually want a green/gray/red lock when we have more information about the actual details per-request. Weak algorithms could be called out in such a way. But until we have that data, a gray lock or nothing seems the right thing to do.
Devin Rousso
Comment 7
2017-11-02 23:24:44 PDT
Comment on
attachment 325863
[details]
[PATCH] Proposed Fix View in context:
https://bugs.webkit.org/attachment.cgi?id=325863&action=review
r=me
> Source/WebInspectorUI/UserInterface/Views/NetworkTableContentView.js:412 > + console.assert(!cell.firstChild, "We expect the cell to be empty.", cell, cell.firstChild);
I'm not sure of the usefulness of this assertion. I understand that it will help catch edge cases, but it also seems to include quite a lot of detail. I personally think that just the check and message is enough, but it's your call.
Joseph Pecoraro
Comment 8
2017-11-03 02:42:31 PDT
The goal of the assertion is for the future. If we ever make Table.js reissue cells then this code could be improved. There is also only 1 column that does an in place update (waterfall) and it lacking the assertion helps make that known.
WebKit Commit Bot
Comment 9
2017-11-03 03:00:26 PDT
Comment on
attachment 325863
[details]
[PATCH] Proposed Fix Clearing flags on attachment: 325863 Committed
r224391
: <
https://trac.webkit.org/changeset/224391
>
WebKit Commit Bot
Comment 10
2017-11-03 03:00:28 PDT
All reviewed patches have been landed. Closing bug.
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