Do you mean build 4.1.0? We haven't released 4.1.1 yet. If you intended to reference build 4.1.0, please update this and other tickets' descriptions (e.g. T96201)

@Vibhabamba Should we have the gray background that desktop has?

@bearND - Thanks for checking. No grey background or bounding boxes are required. The desktop treatment is quite dated. if we fix the whitespace, it will look just fine.

BTW, the examples are from the Hebrew version of the Tel Aviv article, in the section titled המתאר העירוני.

I took a quick look at the DOM.
This element is responsible for the extra white space:
<div style="margin:40px auto;">

This is fixed on Android by my changes in T94646.

Since T94646 is effectively an epic and no more than 50%* likely to be merged this sprint I'm moving this task back to "doing" for a separate fix.

*A made-up probability.

This can be fixed with 2 additional lines of CSS which are generated by a subset of the changes already merged to the .less files in the MobileApp extension (https://gerrit.wikimedia.org/r/#/c/209588/) to accommodate the ongoing work on T94646.

So, like I said, it's an easy fix, but there are a couple of different ways of going about it in the .less files that generate this code:

(Edited directly for demonstration purposes only!)

diff --git a/wikipedia/assets/styles.css b/wikipedia/assets/styles.css
index 2c0a96f..aaef129 100644
--- a/wikipedia/assets/styles.css
+++ b/wikipedia/assets/styles.css
@@ -208,6 +208,10 @@ ul.gallery .gallerybox > div {
 }
 ul.gallery .gallerybox > div > .thumb {
   max-width: 100%;
+  margin: 0 auto;
+}
+ul.gallery .gallerybox > div > .thumb > div {
+  margin: 0 auto !important;
 }
 ul.gallery .gallerybox .gallerytext {
   overflow: hidden;

Is there someone specific from mobile web, an apps liaison, who we can generally turn to for comment on these kinds of design fixes and whether, say, it's a general fix that should go into MobileFrontend, whether it should live in MobileApps, or whether there are unintended consequences of prospective changes? If not, should there be?

So, once again, it looks like this is another task that might have made more sense to be handled by MobileFrontend to begin with, especially since it's just a few lines of CSS that would apply equally to mobile web and apps.
@Jdlrobson @phuedx Would you mind evaluating this CSS change, and see it we can get it into MobileFrontend?

Isn't this the same as T78174 ?
This really shouldn't be something fixed in apps first... but I've told you that before right?

Looking closely no it's a different bug and also impacts mobile web - https://he.m.wikipedia.org/wiki/%D7%AA%D7%9C_%D7%90%D7%91%D7%99%D7%91-%D7%99%D7%A4%D7%95#.D7.94.D7.9E.D7.AA.D7.90.D7.A8_.D7.94.D7.A2.D7.99.D7.A8.D7.95.D7.A0.D7.99 - so please let us fix it in the web first not the app... this hasn't been reported before.

I happily leave it in your hands.

@KHammerstein can you confirm the same should be done for mobile web?

Any sense of priority of this @JKatzWMF ? Should we be getting this fixed asap?

@Jdlrobson Yes same should be done for mobile web

@KHammerstein sure but I want some idea from Jon Katz about how quick we need to have this fixed by... are we aiming for next Android release? When it is that?

@KHammerstein @Jdlrobson @phuedx Sorry for the late response. I think sam with Kaity can and should prioritize this for mobile web.

Is this still an issue? I can't replicate.

Using the link in the task description, I can't replicate the bug either.

@bmansurov I see that there is more whitespace on mobile than on desktop version...this is a very low priority to me. Couldn't replicate on apps.