Jump to content

Talk:Community Wishlist/Wishes/Android app: swimming text body

Add topic
From Meta, a Wikimedia project coordination wiki
Latest comment: 1 month ago by MenkinAlRire in topic Somewhat unavoidable
This page is for discussions related to the Community Wishlist/Wishes/Android app: swimming text body page.

  Please remember to:

Somewhat unavoidable

[edit]

@MenkinAlRire this is somewhat unavoidable and generally has to be handled on a case by case basis for many of the occurrences. For instance larger tables are will simply not fit, unless you give them tiny text. —TheDJ (talkcontribs) 13:56, 29 July 2024 (UTC)Reply

I see. So I am right with my guess, that it derives from elements in the article, that are wider than the body of text. Hence, there is no real cure, if the formatting of the tables is ok. (...other than maybe turning my device into square format). Then I rest my case. MenkinAlRire (talk) 14:19, 29 July 2024 (UTC)Reply
@TheDJ It is not just tables, even simple enumerations and lists obviously can already break the defined text body. That is disappointing.
See e.g. de:Hexenverfolgung#Verfahren bei Hexenprozessen, the format is the simplest and ok in itself. (At first I thought it was a caption.)
Should I then ask for another bug fix?:
the width of lists and enumarations should be limited to the defined overall width of the text, not inherit its value and expand beyond it.
(In the case of tables I understand that it cannot be limited.) MenkinAlRire (talk) 16:31, 29 July 2024 (UTC)Reply
In this particular case it is because there is in an image inside the list. It seems the app makes all images full width of the screen, instead of fullwidth of available width. As the list adds extra indentation, this causes an issue. This doesn't seem to be a problem in the mobile website, so it is an App specific bug, that likely should be fixed. —TheDJ (talkcontribs) 19:15, 29 July 2024 (UTC)Reply
The image inside the list... I saw that, ok then. Thank you. MenkinAlRire (talk) 12:02, 1 August 2024 (UTC)Reply