Page MenuHomePhabricator

MobileFrontend: Sections expanded via mfTempOpenSection collapse when JS is loaded
Open, LowPublicBUG REPORT

Description

Steps to replicate the issue (include links if applicable):

  • Load enwiki:Earth with device emulation set to a mobile device
  • From the Performance tab, apply 4x CPU slowdown and Slow 4G network throttling (for example)
  • Reload the page, click section headers to expand some sections before JS modules from the resourceloader are fully loaded

What happens?:

The sections you expanded before JS is loaded collapse, because of the hidden="until-found" attribute is set.

What should have happened instead?:

The sections you expanded before JS is loaded stay expanded, without the hidden attribute.

Software version (on Special:Version page; skip for WMF-hosted wikis like Wikipedia):

Other information (browser name/version, screenshots, etc.):

Event Timeline

Change #1196802 had a related patch set uploaded (by Func; author: Func):

[mediawiki/extensions/MobileFrontend@master] Toggler: Keep expanded sections when initialising

https://gerrit.wikimedia.org/r/1196802

Change #1196802 had a related patch set uploaded (by Func; author: Func):

[mediawiki/extensions/MobileFrontend@master] Toggler: Keep expanded sections when initialising

https://gerrit.wikimedia.org/r/1196802

Described different problems with different root causes.

Change #1196802 had a related patch set uploaded (by Func; author: Func):

[mediawiki/extensions/MobileFrontend@master] Toggler: Keep expanded sections when initialising

https://gerrit.wikimedia.org/r/1196802

HSwan-WMF moved this task from Incoming/Inbox to Needs Refinement on the Reader Growth Team board.

Hi @Func, thanks for posting.

We are currently working on an experiment around defaulting mobile sections to expanded instead of defaulting them to collapsed. We're going to launch an A/B test around this for a subset of users in a few weeks. Based on the data we get, we may decide to move away from auto-collapsing mobile sections in general.

We can revisit this bug once we have some initial findings here.