Change Details

The ticket T149391 defines so-called 'No-Effect' states for: 1) situations where the user has selected Quality or Intent filters that are subsets of other filters, and 2) situations where the user has selected all filters in a "Full Coverage" group. When the user's filter combinations create a No-Effect state, the filter tags turn gray and a special tooltip is shown. These tooltips are an effort to educate the user about how the filtering tools work. E.g., they tell the user that "selecting all filters in a group is the same as selecting none." Or that the user should "consider highlighting to distinguish." That is all useful info. But it's important to observe that the no-effect state doesn't //harm// the user in any way (unlike the Conflict States). Given this, it seems possible that the tooltips are, at a minimum, TMI, and in many situations actually confusing. Consider the example in the screenshot. The user has selected a filter, Likely Bad Faith, that is redundant with May Be Bad Faith. But he's also highlighted it. The filter is inactive but the highlighting works just fine, because highlighting can't be redundant. However, the screenshot tells him that "The filter has no effect..." "What do you mean," our user might wonder. "The edits are green, just as I wanted. Is this thing broken?" {F6904186} We should consider whether we may want to: # Remove the tooltip in situations where the user is also filtering, above. # Create new tooltips for this situation which says more or less "your filter does nothing but your highlight is working," # Remove the tooltips entirely but leave the grayed out states as hints to what's going on. # Eliminate all elements of the 'No effect' states as just being too complicated.

The ticket T149391 defines so-called 'No-Effect' states for: 1) situations where the user has selected Quality or Intent filters that return subsets of other selected filters, and 2) situations where the user has selected all filters in a "Full Coverage" group. When the user's filter combinations create a No-Effect state, the filter tags turn gray and a special tooltip is shown. Even though he suffers no //harm// from the "No-Effect" state, the tooltip educates him about how the tools work. ==The problem In the situation where the user has selected a filter AND highlighted it, however, the tooltip itself may be doing harm—by confusing the user. Consider the example in the screenshot. The user has selected a filter, Likely Bad Faith, that is redundant with May Be Bad Faith. But he's also highlighted it. The filter is inactive but the highlighting works just fine. However, the tooltip tells him: 1) "The filter has no effect..." and 2) "Try highlighting to distinguish." Our user may well wonder aloud: "What do you mean? I AM highlighting. And it's working just fine. Is this thing broken?" {F6904186} ==The fix To remedy this, let's make a change for this SPECIFIC SITUATION: When a selected filter is 1) __in a No-Effect state__, whether because it is full coverage or a redundant subset, and 2) it is __also highlighted__: - KEEP all the various signals we've defined for No-Effect (graying the tag, etc.). - BUT do not display the special tooltip. - INSTEAD, display the standard tooltip that provides the filter description.

The ticket T149391 defines so-called 'No-Effect' states for: 1) situations where the user has selected Quality or Intent filters that arereturn subsets of other selected filters, and 2) situations where the user has selected all filters in a "Full Coverage" group. When the user's filter combinations create a No-Effect state, the filter tags turn gray and a special tooltip is shown. Even though he suffers no //harm// from the "No-Effect" state, the tooltip educates him about how the tools work. These tooltips are an effort to educate the user about how the filtering tools work. E.g., they tell the user that "selecting all filters in a group is the same as selecting none." Or that the user should "consider highlighting to distinguish." That is all useful info. But it's important to observe that the no-effect state doesn't //harm// the user in any way (unlike the Conflict States).==The problem In the situation where the user has selected a filter AND highlighted it, Given this, it seems possible that the tooltips are, at a minimum, TMI, and in many situations actually confusing. Consider the example in the screenshot. The user has selected a filter, Likely Bad Faith, that is redundant with May Be Bad Faith. But he's also highlighted it. The filter is inactive but the highlighting works just fine, because highlighting can't be redundant. Hhowever, the screenshot tells him that "The filter has no effect..."tooltip itself may be doing harm—by confusing the user. "What do you mean," our user might wonder. "The edits are green,Consider the example in the screenshot. The user has selected a filter, Likely Bad Faith, that is redundant with May Be Bad Faith. But he's also highlighted it. The filter is inactive but the highlighting works just fine. However, the tooltip tells him: 1) "The filter has no effect..." and 2) "Try highlighting to distinguish." Our user may well wonder aloud: "What do you mean? I AM highlighting. just as I wantedAnd it's working just fine. Is this thing broken?" {F6904186} We should consider whether we may want to==The fix To remedy this, let's make a change for this SPECIFIC SITUATION: When a selected filter is 1) __in a No-Effect state__, whether because it is full coverage or a redundant subset, and 2) it is __also highlighted__: # Remove the tooltip in situations where the user is also filtering, above. # Create new tooltips for this situation which says more or less "your filter does nothing but your highlight is working,"- KEEP all the various signals we've defined for No-Effect (graying the tag, etc.). # Remove the tooltips entirely but leave the grayed out states as hints to what's going on- BUT do not display the special tooltip. # Eliminate all elements of the 'No effect' states as just being too complicated.- INSTEAD, display the standard tooltip that provides the filter description.