Page MenuHomePhabricator

Mobile page is "too wide" and can't scroll horizontally in Opera Mini
Closed, ResolvedPublic

Description

Opera Mini Android Version 7.5.32193

Below the search box, the body content has some white margin, and some infoboxes look too wide to fit in the remaining space, causing a column on the right cut off, and no "scrollbar" appears at this time. The desktop works well: although it's wider, it can scroll correctly.

Is this an Opera Mini bug or MF bug?


Version: unspecified
Severity: normal

Details

Reference
bz46726

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 1:31 AM
bzimport set Reference to bz46726.

Related URL: https://gerrit.wikimedia.org/r/63004 (Gerrit Change I5c626be24615f80ec598291f9ed482cadcd787b3)

https://gerrit.wikimedia.org/r/63004 (Gerrit Change I5c626be24615f80ec598291f9ed482cadcd787b3) | change APPROVED and MERGED [by MaxSem]

On live sites, I don't see infoboxes overflowing anymore, but wide images are still cut off on the right, and horizontal scrolling is still impossible.

Can you give an example page that is effected by this problem and post a screenshot? It's not clear what you are referring to...

(In reply to comment #6)

Can you give an example page that is effected by this problem and post a
screenshot? It's not clear what you are referring to...

Ah it's not really this bug, but it's still not displayed perfectly.

Have a look at this page:
https://en.wikipedia.org/wiki/User:Liangent/bug46726

with "Single column view" turned off in Opera Mini's settings.

The image is displayed with some white margin on the left, but no margin on the right, so I was mislead and thought there're a few more pixels out of the view box.

But ideally having some white margin on right too, or scaling the image down to fit them in paragraphs' width looks better, but it might be out of our control.

Give the image class thumb instead of image and you'll be okay.

You are rendering an image with no width parameter so it spills out of the page as it should.

This is one of those situations where more consistent class usage across projects will help with mobile optimisation.

The original issue should be "FIXED".