Page MenuHomePhabricator

Promote 'font changer' to beta
Closed, ResolvedPublic


Get the 'font changer' feature working (seems to be broken currently), and promote it from alpha to beta. May need further discussion on the implementation.

Event Timeline

kaldari raised the priority of this task from to Needs Triage.
kaldari updated the task description. (Show Details)
kaldari added a project: Web-Team-Backlog.
kaldari subscribed.

@KHammerstein, @JKatzWMF We need to figure out what implementation makes sense for this. Apparently Florian built two versions, one that lived on the settings page and one that lived in hamburger menu. I usually don't have strong opinions on these things, but it seems like it would be a lot better for this to live on the settings page, both because it is a more intuitive location and so it doesn't take up valuable space in the hamburger menu. Thoughts?

@kaldari, @KHammerstein: I agree with you that it should sit in settings. Can @Florian provide a screenshot or more of how this implementation works?

@JKatzWMF: There was a discussion about that, with some prototypes and arguments, without quoting them all, i just linking the task :D
T50946: Add font size adjustment feature

There is one prototype (my first one) on Special:MobileOptions:

example.PNG (640×362 px, 27 KB)

I think it's "enough" to discuss it, it would be relatively easy to replace the three buttons (-, size (combined with switch to 100% iirc), and +) with three fixed font size buttons (like we have actually in the drawer).

Btw.: The drawer is available now on wikipedias, but i'm not sure, why it wasn't instantly :(

@JKatzWMF: What do you think about the above example?

@Florian this looks good to me and sorry for the delayed response. Two Quick Questions:

  • what is the action that occurs when you hit the +/- buttons. @KHammerstein suggests 10%.
  • can we swap the explanation to below the buttons?
  • what is the action that occurs when you hit the +/- buttons. @KHammerstein suggests 10%.

Exact, 10%, iirc correctly, but if not, 10% sounds good :)

  • can we swap the explanation to below the buttons?


Change 229950 had a related patch set uploaded (by Florianschmidtwelzow):
Rewrite fontchanger to live in mobile settings now

Change 229950 merged by jenkins-bot:
Rewrite fontchanger to live in mobile settings now

@Florian @Jdlrobson @phuedx

I've noticed what this does internally is set up style attributes on the p tags on the article content.

This results in not all the font sizes being smaller (infobox, etc), but only some text paragraphs:

Screen Shot 2015-08-14 at 11.58.21 AM.png (611×367 px, 82 KB)

I think a better implementation would be setting a font-size of 70% on the body or if we don't want the whole UI to change on #bodyContent so that it only affects the content.

This is the #bodyContent { font-size: 70% }:

Screen Shot 2015-08-14 at 12.00.58 PM.png (595×366 px, 84 KB)

As you can see it scales all the content very nicely since we're not using fixed pixels anywhere (which btw is awesome).

@Florian I loved that reseting to 100% didn't do anything weird like setting the ps with style='font-size: 100%;'. Very nice touch!

My recommendation would be to set it on body so that the font changes affect to all UI elements (let's think you want it bigger or smaller, you probably also want the menu to be bigger or smaller), but I'm open to setting it on #mw-mf-page-center for the whole UI minus the menu or #bodyContent for only the article content.

Opinions? This is very nice!

Some screenshots:

Whole UI at my preferred 70%:

Screen Shot 2015-08-14 at 12.05.20 PM.png (509×369 px, 54 KB)

Whole UI with menu at my preferred 70%:
Screen Shot 2015-08-14 at 12.05.31 PM.png (488×368 px, 43 KB)

For comparison this are the 100% sizes:

Screen Shot 2015-08-14 at 12.05.44 PM.png (556×368 px, 59 KB)

Screen Shot 2015-08-14 at 12.05.53 PM.png (493×366 px, 50 KB)

Same changes apply to making everything bigger to see better or vision problems (120% for example):

Screen Shot 2015-08-14 at 12.09.28 PM.png (581×368 px, 61 KB)

Screen Shot 2015-08-14 at 12.09.40 PM.png (604×369 px, 66 KB)

Moving this back, since we can do better :D

I think this task should be closed and split out into bugs personally. I'm a bit lost what needs to be done before completing this task which is simply to move it to beta.

@Jdlrobson Any opinions from my comment? Otherwise I can update the description with concrete steps about what to do.

@Jhernandez yup I agree with what you're saying I just think it doesn't belong in a card about pushing it to beta as the feature is now in beta (given we have no dev branch) and I think it would be clearer for all involved. Sound okay?

Jdlrobson claimed this task.

Spun off T109363 and resolving this since the original task was simply to get this into beta. Leaving to you for sign off if that makes sense.

We're good. I'm going to swap the blockers around, since the other task doesn't block this one.

Ignore me. This task is fine and there's no blockers to swap. I confused this one with the font changer to stable card.