Unstructured filters replaced by Structured filters may still affect the results
Closed, ResolvedPublic
Actions

Description

When viewing the new UI (structured filters), data may seem incomplete because legacy/invisible filters may still modify the query.

Steps:

Make sure you are logged in and RC Filters beta is disabled
In Preferences/RC, check "Show only edits that may have problems (and hide probably good edits)"
Enable the RC Filters beta
In Preferences/RC, notice that "Show only edits that may have problems (and hide probably good edits)" is not available anymore since it doesn't apply to the new UI (requires reload)
On Special:RC, probably good edits are hidden

Note: there's isReplacedInStructuredUI in the filters definition but it doesn't seem to be used anywhere. Maybe the idea behind this field was to prevent this problem...

Details

Related Changes in Gerrit:

	Subject	Repo	Branch	Lines +/-
	WIP: RCFilters: Keep the default for replaced filters, but allow override	mediawiki/core	master	+0 -4
	RC Filters: Disable defaults for legacy filters in structured UI	mediawiki/core	master	+9 -3

Customize query in gerrit

Related Objects

Mentioned In: T176172: Translate deprecated edit-review search parameters so they work in the new UX
Mentioned Here: T176172: Translate deprecated edit-review search parameters so they work in the new UX
rMW6314a9026f9b: WLFilters: set default values
T159763: Enable parts of ORES extension by default and manage impacts on the RC Page and the RC page Preferences tab

Event Timeline

SBisson created this task.Apr 4 2017, 3:21 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 4 2017, 3:21 PM

The field is used to export a data attribute that causes the client-side JS to hide the filter. You're right that we may need to use it to ignore the filter.

I think the solution here is to set all the defaults to not-hide for legacy filters, if the Beta Feature is enabled. That way, they still display on the page and the URL still works (both helpful for no-JS and backwards-compatibility), but if it's not in the URL, it will never hide based on a default.

This can be done by core itself based on a getter for isReplacedInStructuredUi.

I think that's a good approach, because we do need the params to still work (for no-JS).

SBisson claimed this task.Apr 5 2017, 1:08 PM

SBisson edited projects, added Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017); removed Collaboration-Team-Triage.

SBisson moved this task from Untriaged to In Development on the Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017) board.

Change 346548 had a related patch set uploaded (by Sbisson):
[mediawiki/core@master] RC Filters: Disable defaults for legacy filters in structured UI

https://gerrit.wikimedia.org/r/346548

gerritbot added a project: Patch-For-Review.Apr 5 2017, 1:52 PM

SBisson moved this task from In Development to Needs Review on the Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017) board.Apr 5 2017, 1:53 PM

Change 346548 merged by jenkins-bot:
[mediawiki/core@master] RC Filters: Disable defaults for legacy filters in structured UI

https://gerrit.wikimedia.org/r/346548

ReleaseTaggerBot added projects: MW-1.29-release (WMF-deploy-2017-04-25_(1.29.0-wmf.21)), MW-1.29-release-notes.Apr 12 2017, 10:00 PM

SBisson moved this task from Needs Review to QA Review on the Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017) board.Apr 13 2017, 12:38 PM

Checked the fix in cawiki betalabs (enwiki betalabs does not have the option 'Show only edits that may have problems (and hide probably good edits)' in Preferences-Recent Cchanges):

Note (minor): From users' point of view it might look as an interruption of established workflow - if I had the option 'Show only edits that may have problems (and hide probably good edits)' checked, I would reasonably expect this setting to be transferred along with my other RC settings to my selection of filters when I enable 'New filters for edit review'.

QA Recommendation: Product should weigh in

Etonkovidova moved this task from QA Review to Product Review on the Collaboration-Team-Triage (Collab-Team-Q3-Jan-Mar-2017) board.Apr 13 2017, 7:49 PM

Thanks for the note @Etonkovidova. It's a good point. This change is specified in T159763. Yes, looking back, we could have kept this preference and worked it so that it simply selected the "May have problems" filter as a user default. I don't remember why we got rid of it. But at this point, I think we are moving forward to a model where users specify RC Page defaults on the RC Page. That will be superior. So let's move forward with this but look out for users who mention the issue.

Change 376794 had a related patch set uploaded (by Mattflaschen; owner: Mattflaschen):
[mediawiki/core@master] WIP: RCFilters: Keep the default for replaced filters, but allow override

https://gerrit.wikimedia.org/r/376794