Background
Following the deploy we can remove 7kb of compressed JavaScript from initial page load on mobile and delete over a 1000 lines of unused code.
User story
As a user I don't want to load unused unmaintained code in my mobile experience.
Requirements
- We have checked that WMDE have responded to the removal (T395641: Wikidata typeahead customization is not compatible with Minerva)
- Code calling out to Minerva's search overlays is removed from Minerva (https://gerrit.wikimedia.org/r/c/mediawiki/skins/MinervaNeue/+/1152180)
- Code relating to MobileFrontend's search feature is removed (https://gerrit.wikimedia.org/r/c/mediawiki/extensions/MobileFrontend/+/1138811)
- All associated configuration has been cleaned up.
BDD
Feature: Mobile search uses core TypeaheadSearch without legacy Minerva/MobileFrontend search code
Scenario: Mobile search works at standard viewport
Given I am on a mobile wiki page
When I focus the search input
Then typeahead search suggestions are shown and are usable
Scenario: Mobile search works at narrower viewport with search icon affordance
Given I am on a mobile wiki page at a lower resolution where a search icon is shown
When I tap the search icon
Then the search field focuses and typeahead search suggestions are shown and are usable
Scenario: No legacy Minerva search overlay behavior
Given the new TypeaheadSearch is active
When I interact with search
Then no Minerva-specific search overlay UI appears
Scenario: Watchlist features remain functional
Given I have items in my watchlist
When I view Watchlist and use watch/unwatch controls
Then watchlist renders correctly and watchstars function as expected
Scenario: No visual regressions versus production
Given I compare the updated mobile experience to production
When I use search and browse common pages
Then the UI matches production behavior and appearanceTest Steps
Test Case 1: Verify mobile search at standard viewport
- Open any article on the mobile site (Minerva skin).
- Focus the search input.
- AC1: Typeahead suggestions appear and update as you type.
- AC2: Selecting a suggestion navigates correctly.
- AC3: No Minerva legacy search overlay appears (UI is Codex/core TAHS).
Test Case 2: Verify mobile search at lower resolution with search icon
- Resize/emulate a narrower mobile viewport where a search icon is shown.
- Click/tap the search icon.
- AC4: The search field focuses and the suggestions panel opens.
- AC5: Suggestions behave correctly (navigate with touch/keyboard, select, navigate).
- AC6: No legacy search overlay behavior appears.
Test Case 3: Validate watchlist remains functional
- Ensure AMC is disabled in settings.
- Go to Special:EditWatchlist/raw and add several pages.
- Visit Special:Watchlist.
- If needed, click “View and edit watchlist” tab.
- AC7: Watchlist loads and displays items as expected.
- AC8: Watch/unwatch (watchstar) controls work (state updates on click, persists on refresh).
Test Case 4: Compare against production for regressions
- In one window, open the updated beta/mobile site; in another, open production/mobile for the same pages.
- Exercise search (focus, type, select), page navigation, and watchstars on both.
- AC9: No visual or behavioral regressions versus production for mobile search and general UX.
QA Results - Beta
| AC | Status | Details |
|---|---|---|
| 1 | ✅ | T395634#11076546 |
| 2 | ✅ | T395634#11076546 |
| 3 | ✅ | T395634#11076546 |
| 4 | ✅ | T395634#11076546 |
| 5 | ✅ | T395634#11076546 |
| 6 | ✅ | T395634#11076546 |
| 7 | ✅ | T395634#11076546 |
| 8 | ❓ | T395634#11076546 |
| 9 | ✅ | T395634#11076546 |
QA Results - Prod
| AC | Status | Details |
|---|---|---|
| 1 | ✅ | T395634#11109335 |
| 2 | ✅ | T395634#11109335 |
| 3 | ✅ | T395634#11109335 |
| 4 | ✅ | T395634#11109335 |
| 5 | ✅ | T395634#11109335 |
| 6 | ✅ | T395634#11109335 |
| 7 | ✅ | T395634#11109335 |
| 8 | ⬜ | T395634#11109335 |
| 9 | ✅ | T395634#11109335 |
Design
- Add mockups and design requirements
Acceptance criteria
- Add acceptance criteria
Communication criteria - does this need an announcement or discussion?
- Add communication criteria
Rollback plan
- What is the rollback plan in production for this task if something goes wrong?
This task was created by Version 1.2.0 of the Web team task template using phabulous
