1960756 - Decision Log in about:support says "Blocklisted" even if actually it is not

Status: NEW

(Core :: Graphics, defect, P2)

Description

[Masatoshi Kimura [:emk]]

Steps to reproduce:

1. Open troubleshooting information on Windows
2. Look at the DIRECT2D section.

Actual result:
Blocklisted; failure code FEATURE_FAILURE_DISABLED

Expected result:
Something other than "Blocklisted".

Comment 1

[Masatoshi Kimura [:emk]]

Regression range: https://hg-edge.mozilla.org/mozilla-central/pushloghtml?fromchange=a29b80b107103df84e493008e420e30aea857da1&tochange=82670c05383339b7547ed4c4099b00028a29a5a2

I guess bug 1801780 is the regressor. Before this bug, the message was something like "disabled by user: Disabled via gfx.direct2d.disabled". Bug 1801780 repurposed "unknown-failure" l10n entry to use for all messages without a bug number. It makes the "Blocklisted;" part of the message redundant because we have the status column whose content is disabled/failed/blocked/blocklisted/etc.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1801780

:aosmond, since you are the author of the regressor, bug 1801780, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Comment 3

[Masatoshi Kimura [:emk]]

Some thoughts:

• "failure" should also be removed because "disabled by default" should not be considered as a failure IMO. The current message is misleading. I was worried that my hardware might be old until I realized that "Blocklisted; failure code" was just a template.
• "#BLOCKLIST_FEATURE_XXX" in the third column is also redundant because the same information is repeated in the fourth column.

Comment 4

[Dianna Smith [:diannaS]]

:bhood if possible, can you set a priority/severity for this?

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1801780