Page MenuHomePhabricator

Content checklist for making AdvancedSearch a default feature
Open, MediumPublic

Description

  • We have covered the topic of accessibility
  • We proactively lazy load hidden forms
  • Namespaces can still be used quickly, without having to switch between input media (mouse, keyboard)
  • We don't provide the feedback link anymore

Background
This is a tracking ticket of WMDE's Technical Wishes project.
It is meant to help us remember everything that we need to check before turning a beta feature into a default feature.

Event Timeline

Lea_WMDE created this task.Jul 2 2018, 8:56 AM
Restricted Application added a project: archived--TCB-Team. · View Herald TranscriptJul 2 2018, 8:56 AM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Lea_WMDE triaged this task as Medium priority.Jul 31 2018, 8:48 AM
Lea_WMDE updated the task description. (Show Details)
Lea_WMDE updated the task description. (Show Details)Jul 31 2018, 9:21 AM
Lea_WMDE updated the task description. (Show Details)Jul 31 2018, 9:37 AM
Lea_WMDE updated the task description. (Show Details)Aug 3 2018, 11:52 AM

Removed the hook criterion. We build the hook, once somebody says that they want to use it.

Tgr added a comment.May 10 2020, 3:10 PM

Nvm, it seems like the hook already exists.

Aklapper renamed this task from Content checklist formaking AdvancedSearch a default feature to Content checklist for making AdvancedSearch a default feature.May 10 2020, 3:22 PM