Page MenuHomePhabricator

Confusing behavior of long references
Open, MediumPublicBUG REPORT

Description

I am not sure what is the proper (designed/expected) behavior of the reference display popup, but is very confusing to me. Only when preparing this bug report, I noticed the window can be enlarged by pulling the caption. Sometimes.

The contents can sometimes be scrolled. Sometimes a little bit, sometimes more. But at the end, there is no indication the reference text continues, it is just cut short, and only be pulling the title bar to maximize the popup, the rest (including the navigation dots when multiple references are at one place) is displayed. But if the clicked reference is short, the navigation dots are shown there. Sometimes. Dunno.

Steps to reproduce

  1. In the app, go to e.g. [[en:Monarchy of Canada#Personification of the Canadian State]].
  2. In the first paragraph of the section, click on the [130] footnote. The whole text of the footnote appears, with no navigation dots at the bottom. But still, you can navigate to the previous reference by pulling from the left. Or, you can pull the title bar up to show the navigation dots.
  3. Or, click on [n 11] instead. By dragging the text, you are able to scroll down… until “and past Ontario”, no going further, and no navigation dots visible. By pulling the title bar up, the popup is maximized, all text is reachable by scrolling, including the navigation dots at the bottom.
  4. Click on [129] instead. You are shown just the first line of the reference, and the navigation dots below it. The popup seems not to be enlargable at all, pulling the title bar does nothing. So you are unable to view the rest of this and other references at all.

Expected results

Dunno, something consistent?

Environments observed

App version: 2.7.50324-beta-2020-06-29
Android OS versions: 9
Device model: G8441 (Sony Xperia XZ1 Compact)
Device language: Czech (cs)

Event Timeline

LGoto added subscribers: Charlotte, LGoto.

@Charlotte Is this a regression? Can you set a priority so PI knows how important this is for Android? Thanks!

@Charlotte Is this a regression? Can you set a priority so PI knows how important this is for Android? Thanks!

Priority set. The refs did not act this way before mobile-html.