Update OOUI to match new Vue search UI & UX
Open, MediumPublic
Actions

Assigned To

None

Authored By

	alexhollender_WMF
	Jan 25 2021, 5:10 PM

Description

In T249299 we built a new search component using Vue.js (currently implemented in Vector as the main search in the site header). There are some differences between the new search component and the OOUI search component (used elsewhere on the site, e.g. Advanced search, Insert link, etc.). This task is for figuring out what our plan is in order to achieve (or at least increase) consistency between the new search component and the existing one.

Differences between the two search experiences

bolding of page titles in search results (additional context here)

Plan

Option A) replace all existing search components with the new one
Option B) update the existing search component to match the new one
Option C)

Related Objects
Search...

Status	Assigned	Task
Open	None	T177251 Dead keys prevent autocomplete in search box
Resolved	ovasileva	T244392 [GOAL] Deploy the new Vue.js search experience
Resolved	Volker_E	T249299 [Epic] Build the new Vue.js search experience
Open	None	T272873 Update OOUI to match new Vue search UI & UX

Event Timeline

alexhollender_WMF created this task.Jan 25 2021, 5:10 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJan 25 2021, 5:10 PM

@Volker_E this is a placeholder task that came from @Esanders pointing out a difference between our new search experience and what's in OOUI. I know you've already started thinking about this so please feel free to close or restructure as you see fit.

alexhollender_WMF updated the task description. (Show Details)Jan 25 2021, 5:13 PM

alexhollender_WMF added a parent task: T249299: [Epic] Build the new Vue.js search experience.

alexhollender_WMF mentioned this in T272625: Add “Typeahead” search component to DSG.Jan 25 2021, 8:22 PM

I note that the desktop search widget also expands the left padding when open to keep the query aligned with results (as discussed in T255603). I don't think that extends well to a generic widget where we don't know if there is space to do that animation. I think this lack of generalisability should factor in to the decision about whether we keep that feature.

ovasileva triaged this task as Medium priority.Jan 27 2021, 4:09 PM

ovasileva moved this task from Needs Prioritization to Triaged but Future on the Readers-Web-Backlog board.

Jdlrobson moved this task from Triaged but Future to Tracking on the Readers-Web-Backlog board.Apr 30 2021, 9:18 PM

Jdlrobson edited projects, added Readers-Web-Backlog (Tracking); removed Readers-Web-Backlog.

Jdlrobson added projects: OOUI, UI-Standardization.Nov 5 2021, 5:57 PM

Jdlrobson moved this task from Untriaged to Untag on the Readers-Web-Backlog (Tracking) board.

LGoto removed a project: Readers-Web-Backlog (Tracking).Nov 9 2021, 4:23 PM