This can be tested once T269093: Deploy new language switching location to test wikis and begin A/B test pt 1
Over to @MNeisler for some thoughts.
Declining as per the comment above. We currently do not support IE11 on the mobile site.
Fri, Jun 11
@MNeisler - seems like we're all done here! I'm going to go ahead and resolve but feel free to re-open in case there's anything missing
Thu, Jun 10
Wed, Jun 9
WE can decline for now
This is also quite old. I'm going to go ahead and resolve. @alexhollender - let me know if you'd like to keep it open.
Declining this for now as PDFs have dropped in priority over the past few years.
Tue, Jun 8
Moving to backlog for now - @Volker_E - feel free to bring this back into the sprint board whenever
Can we backport this? Generally, this wouldn't be a blocker, but since there's no train next week, it would be nice to get a fix out sooner than the next train.
Rough set of questions;
- How does usage of the links decrease or increase before and after usage of the feature. For this, we will not be performing an A/B test, but rather a before and after comparison between the current implementation (for which we should have historical data via the DesktopWebUIActionsTracking schema and compare to the current implementation. Open question for this spike - does the new version track events in a similar way?
- Do these changes affect account creation - it's possible we might see an increase or decrease here. For this we would do a before/after comparison. Note: we're already tracking this in the desktop improvements superset dashboard: https://superset.wikimedia.org/superset/dashboard/153/
Thank you for opening this @phuedx!
Mon, Jun 7
Let's keep this task on hold for right now - tagging it as low, but would like to revisit once we have more data on the opt-outs from T269664: Determine opt-out rate for desktop improvements feature on test wikis pt 2
@alexhollender, @Jdlrobson - just to confirm the change to the AC: "At lower resolutions the search input is hidden search and only the submit button is shown. It should behave like a form submit link (e.g. submit the form with no input value). We'll wire this up in a later task T284242."
@Volker_E - any updates on this one? If we're not planning on tackling it in the near future, I'd support moving it back to the backlog for now.
Fri, May 28
All found bugs are now tracked, resolving!
Thu, May 27
All done, resolving!