Open Bug 1553026 Opened 6 years ago Updated 2 years ago

Show long-form blocked reason for blocked resources in the details sidebar

Categories

(DevTools :: Netmonitor, enhancement, P3)

enhancement

Tracking

(Not tracked)

People

(Reporter: Harald, Unassigned)

References

(Blocks 1 open bug)

Details

User Story

When inspecting a blocked resource, I want to see the reason for blocking in long form, so that I don't just have to depend on seeing the reason in a small table column.
No description provided.
User Story: (updated)

What if we also rendered "Blocked" label in the Status column, which is currently empty? We can use the same styling as for valid status or as for "Failed" requests.

Consequently we wouldn't need to use "Blocked by" prefix in the Transferred column, which would safe space (currently I mostly see only "Blocked By" in that column)

Honza

Flags: needinfo?(hkirschner)
No longer blocks: 1157817
Depends on: 1157817

What if we also rendered "Blocked" label in the Status column, which is currently empty? We can use the same styling as for valid status or as for "Failed" requests.

That also aligns with Chrome, so I would be in favor. The status column is also not very wide, so will hit the same issue of wide text – or am I missing something?

Flags: needinfo?(hkirschner)

(In reply to :Harald Kirschner :digitarald from comment #2)

What if we also rendered "Blocked" label in the Status column, which is currently empty? We can use the same styling as for valid status or as for "Failed" requests.

That also aligns with Chrome, so I would be in favor. The status column is also not very wide, so will hit the same issue of wide text – or am I missing something?

The idea is around the following:

  • The Status column would display just Blocked label (which corresponds to the status of the request). The Blocked label would have a tooltip showing the long-form blocking reason.
  • The Transferred column would continue displaying the the blocking reason but, without the "Blocked by" prefix.
    Example:
    Instead of blocked by Mixed Block we do Mixed Block only

If the long form has always Block postfix it's clear that it's about blocking and the important part is at the beginning.

Honza

SGTM, seems a bit easier to understand than Chrome only showing it in one column! One risk is that users will not discover the tooltip in the BLOCKED status; maybe we can be creative there.

Summary of tasks for this bug:

  1. Display Blocked label in the Status column (using the same style as for status code)
  2. Display long-form blocking reason in a tooltip for the Blocked label
  3. Display long-form blocking reason in a Headers side panel (in the summary section at the top of the panel)
  4. Display blocking reason in Transfer column (with no additional 'blocked by' prefix). In case we have short-form blocking reason (e.g. 'CSP Block' for various CSP blockers) we could use it for the Transfer column (columns tend to be thin).
  5. Display long-form blocking reason tooltip for the Transfer column.

Honza

Depends on: 1556451
No longer depends on: 1556451
Blocks: 1484005
No longer blocks: devtools-resource-blocking
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.