Page MenuHomePhabricator

Mobile version image caption is placed on top of image in iOS
Closed, ResolvedPublic

Event Timeline

Jdlrobson subscribed.

I cannot reproduce on web. I think this might be fixed?

Cannot reproduce either. @Yanpas: Does this still happen? Which browser and version?

I use ios 8.1 Safari and still reproduce

Jdlrobson renamed this task from Mobile version image caption is placed on top of image to Mobile version image caption is placed on top of image in iOS.Jan 25 2017, 8:32 PM

Appears to be reproducible. Does this need additional info or should it be moved?

@ABorbaWMF is it all Safari's or just ios 8.1? Do other browsers have the issue?
Feel free to move to "Triaged but future" whenever you can reproduce things like this so we can take a look.

Half a year ago everything wak ok

So far I have been unable to reproduce this bug on the following platforms using the example URL:
iPhone 5s iOS 10.2
iPad Mini Retina iOS 10.2
iPad Mini iOS 9.3.5

Based on the screenshot, this may have been a phone issue. The layout is different on iPad. So I could look at it on some more phones on older iOS versions.

I cannot reproduce it in the iOS simulator. @ABorbaWMF am I assuming correctly that you've been testing on real devices?

Yes, testing on a limited number of real devices (so far)

Since we can't reproduce from our side, I am closing this for now. @Yanpas - let us know if you run into this again/if you can give us some steps to reproduce

We can reproduce but only on a real device.

I've reproduced this on iPhone 6S and 7 (iOS 10.2) and Samsung-SM-J120A/Galaxy Express 3 (Android 6.0.1). In both cases I used the latest app builds as of this writing - 5.4.0 (1060) for iOS and 2.4.184-alpha-2017-02-01 for Android. According to the screencaps I've taken, at least with these devices and builds it is displaying as expected now

T155136 iOS 10.2.PNG (1×750 px, 963 KB)

T155136 Android 6.0.1.png (800×480 px, 373 KB)

ABorbaWMF claimed this task.

I think this can be closed at this point. I don't think @Nicholas.tsg was able to reproduce the bug nor was I.