Estimating a 2 for the solution for frwiki, will set up a parent ticket tracking solutions for other projects
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Yesterday
Looks like we have clear next steps in T362939: Fix unintended vertical spacing behavior in Minerva and Vector. Resolving this one.
Looks good, resolving.
Trying to test on beta today and the menu is no longer available for logged-out users.
Note that we should link to this ticket and the Miro board once we have mw documentation set up for this work
Everything looks good, resolving
In T358904#9723667, @bwang wrote:In T358904#9664446, @ovasileva wrote:We do want the codex search in there eventually, though, right? That would give us a responsive search across Vector and Minerva. cc @ovasileva .
We do want the codex search eventually. I think the plan was to do that work as we're looking into the search empty state so that we can combine efforts across desktop/mobile. I can set up a separate goal ticket that can collect all the work related to that.
@ovasileva did you ever get the chance to make the goal for replacing the Mobile search with codex?
Seems most straightforward to re-use this ticket
Thu, Apr 18
@Jdrewniak to update with current plan and write out follow-up ticket before closing.
@thcipriani - this one is not maintained by the web team, but we're not sure what to more accurately tag it with either. Untagging for now
In T362338#9724896, @Jdlrobson wrote:@ovasileva this is fixed now. I asked @JScherer-WMF about linking to both "Saved" and "Watchlist" and separating these features and linking to both and he was in support.
What do you think? Should we create a follow up ticket?
Full context: https://phabricator.wikimedia.org/T362338#9720869
Looks good. Resolving. Will test in production once we make the changes
Wed, Apr 17
In T360098#9720796, @Edtadros wrote:Thanks @SToyofuku-WMF!
@ovasileva, before I update the description with BDD and Test Steps, I wanted to get your approval of the requirement v2 in the description. I wasn't sure how to incorporate the "In the future" requirement bullet, because I wasn't sure how this could be validated. Let me know what you think.
Tue, Apr 16
Reopening after further investigation and additional feedback received
All done here, thank you @jwang!
Looks good, resolving!
Mon, Apr 15
We don't always expect there to be contrast issues, but rather situations where contrast issues might appear in the future due to specific uses of templates. We will document this as part of signoff.