Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(144)

Issue 2208803002: Remove SCT counters from DevTools security panel (Closed)

Created:
4 years, 4 months ago by estark
Modified:
4 years, 4 months ago
Reviewers:
lgarron, pfeldman
CC:
lgarron, apavlov+blink_chromium.org, blink-reviews, blink-reviews-api_chromium.org, caseq+blink_chromium.org, chromium-reviews, darin-cc_chromium.org, devtools-reviews_chromium.org, dglazkov+blink, Eran Messeri, jam, kozyatinskiy+blink_chromium.org, lushnikov+blink_chromium.org, pfeldman+blink_chromium.org, pfeldman
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Remove SCT counters from DevTools security panel This CL concerns the information that the DevTools security panel shows for the Signed Certificate Timestamps (SCTs) that were served on a request. (SCTs are part of the Certificate Transparency project.) Each SCT has a validation status, and initially (in https://codereview.chromium.org/1589703002), the security panel showed a count of how many SCTs were served with each status. Later, in https://codereview.chromium.org/1772603002, we added the full details of each SCT to the security panel. Thus the counters are now somewhat redundant: we show "X valid SCTs" followed by a summary of each SCT with its validation status. This CL removes the counters ("X valid SCTs, Y invalid SCTs, ..."). While the counters are a little more scannable at a glance, they clutters the UI with redundant information and present an extra burden for maintaining the plumbing needed to show the counters. This is relevant right now because we want to add an additional SCT status. We could rework the plumbing to accommodate this additional SCT status, but it seems to make more sense to just remove the redundant information from the UI. BUG=591848, 634006 Committed: https://crrev.com/46add67f297acfab8c50a7b267a15740b70c1ae9 Cr-Commit-Position: refs/heads/master@{#409666}

Patch Set 1 #

Messages

Total messages: 20 (12 generated)
estark
dgozman, PTAL?
4 years, 4 months ago (2016-08-03 18:55:23 UTC) #5
estark
Actually, switching over from dgozman to pfeldman since I'll need content approval anyway. pfeldman, PTAL?
4 years, 4 months ago (2016-08-03 18:56:22 UTC) #7
estark
Also, here are before and after screenshots for this change: Before: https://drive.google.com/file/d/0B-v7-yE5qU2sbkZOOWNHU05acnM/view?usp=sharing After: https://drive.google.com/file/d/0B-v7-yE5qU2sUDRya1RhM3M4Snc/view?usp=sharing (Note ...
4 years, 4 months ago (2016-08-03 19:30:47 UTC) #8
pfeldman
lgtm
4 years, 4 months ago (2016-08-03 22:16:24 UTC) #12
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2208803002/1
4 years, 4 months ago (2016-08-03 23:37:13 UTC) #14
commit-bot: I haz the power
Committed patchset #1 (id:1)
4 years, 4 months ago (2016-08-03 23:42:26 UTC) #16
commit-bot: I haz the power
Patchset 1 (id:??) landed as https://crrev.com/46add67f297acfab8c50a7b267a15740b70c1ae9 Cr-Commit-Position: refs/heads/master@{#409666}
4 years, 4 months ago (2016-08-03 23:43:30 UTC) #18
lgarron
4 years, 4 months ago (2016-08-04 01:19:20 UTC) #20
Message was sent while issue was closed.
LGTM.

This should be completely safe to remove, since the certificateValidationDetails
value was only used iff it was present.

Powered by Google App Engine
This is Rietveld 408576698