Last modified: 2012-09-21 20:04:59 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T40206, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 38206 - Leading on Today's Featured Article messed up when it has no image (iOS, v.3.1.2)
Leading on Today's Featured Article messed up when it has no image (iOS, v.3....
Status: RESOLVED FIXED
Product: Wikimedia Mobile
Classification: Unclassified
Generic (Other open bugs)
.5
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-05 18:54 UTC by Ryan Kaldari
Modified: 2012-09-21 20:04 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Ryan Kaldari 2012-07-05 18:54:50 UTC
For some reason the leading on "Today's Featured Article" is screwed up. It looks fine on any regular articles, but looks bad on the home page.
Comment 1 Ryan Kaldari 2012-07-06 02:23:01 UTC
Weird, it looks fine now. I wonder if it had something to do with that Featured Article not having an image. That's the only difference I can think of.
Comment 2 Jon 2012-07-24 19:22:37 UTC
Can't replicate so closing to keep bug noise level down.
Comment 3 Ryan Kaldari 2012-09-19 17:00:42 UTC
Reopening since I saw the same problem when the Main Page featured an imageless article again recently.
Comment 4 Jon 2012-09-19 17:39:58 UTC
INext time it happens could you take a closer look at what's going on and try to articulate why this is happening? It's obviously specific to certain articles as it only happens every now and again.

Otherwise this bug is likely to stay open for 4 years with no activity.

I'm keen to get to the point where __all bugs__ in bugzilla for mobile projects are actionable. e.g. they provide a path to replicate the issue, they explain what is wrong with it ("screwed up" is not very precise :-)) and what the expected behaviour is.

I believe when we get to this point we provide a better route for newbies into mediawiki development. Sorry if I sound like an arse but I firmly believe this is the way forward !

You say the problem occurred due to the featuring of an imageless article - was this the case for the original bug report?

How is it screwed up - can you provide a screenshot? Is this a margin issue, is the text unreadable?

I suspect this is an issue with the template being used for the main page rather than an issue with mobilefrontend - it would be good to get to the bottom of this.
Comment 5 Ryan Kaldari 2012-09-19 17:54:58 UTC
Found the problem. The line-height only gets applied if the text is inside a <p> or in a div with id 'featured_article':

p, li, dl, #featured_article {
   line-height: 1.65;
}

However, the featured article div isn't IDed as 'featured_article'. Instead it's IDed with the rather mysterious 'mp-tfa', which gets no styling.
Comment 6 Ryan Kaldari 2012-09-19 17:55:53 UTC
The reason it works if there is a picture is that this triggers the text being put in a <p> tag.
Comment 7 Ryan Kaldari 2012-09-19 17:56:53 UTC
Oh, I guess 'mp-tfa' must be Main Page - Today's Featured Article :)
Comment 8 Ryan Kaldari 2012-09-19 18:01:52 UTC
I guess the best solution would just be to add '#mp-tfa' to the existing list in the CSS. So:

p, li, dl, #mp-tfa, #featured_article {
   line-height: 1.65;
}

Not sure what file this is in, but it's gotta be one of the CSS files included in the MobileFrontend modules.
Comment 9 Jon 2012-09-19 18:05:44 UTC
Anything with the mp- prefix gets added to the main page - everything else gets
scrubbed.  This is also wikipedia specific so should not be put in mobile frontend core.

So where does the issue lie?
* Can we add a generic css rule in mobile frontend?
* Should wikitext be changed to make sure these go in a p
* Is there something we can do in the template to ensure this get dealt with e.g. add an already supported class add an id #featured_article ?
Comment 10 Jon 2012-09-21 20:04:59 UTC
https://gerrit.wikimedia.org/r/24582

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links