Page MenuHomePhabricator

Re-consider font size and font-family for form elements in Vector
Closed, InvalidPublic

Description

screenshot using firefox on windows showing upload wizard form inputs with font-sizes annotated

Currently, Upload Wizard defines font-family: sans-serif for most of its form elements. After the "typographical refresh", this, together with the slightly smaller font-family, produces a misaligned output.

https://commons.wikimedia.org/w/index.php?title=Commons%3AVillage_pump&diff=120509714&oldid=120505191


Attached:

UpWiz_font-family_and_font-size.png (396×640 px, 20 KB)

Details

Reference
bz63408

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 3:07 AM
bzimport added a project: UploadWizard.
bzimport set Reference to bz63408.
bzimport added a subscriber: Unknown Object (MLST).

Created attachment 15004
more drastically on ff/linux

Attached:

openSUSE.png (230×920 px, 20 KB)

Thanks for taking the time to report this!

How does this create an accessibility problem (anybody could increase the font size in th browser)?

(In reply to Andre Klapper from comment #2)

anybody could increase the font size in th browser

The aim of the "typographical refresh" refresh update was I think to not have people to fiddle around with their browser settings.

yeah, form elements do not inherit font family from their offset parents, so you may start a separate bug for this, as if you like to add something similar to

input,select,textarea { font-family:inherit; font-size:inherit; }

but note that UpWiz explicitly defines sans-serif for some classes used on input elements in it.

It is fiexed now? It looks like no?
@Rillke: I guess we can fix this in the global .ccs?

(In reply to Steinsplitter from comment #5)
Why is this a major issue? The text is still readable by most people. Or does it even look worse for you than the screenshots I attached?

Yes, we could attempt to "fix" it but applying extra-css often causes many side effects and I'd really like to see it fixed by someone running browser tests before or having a very good understanding of what could happen. Leaving the side effects aside, there is still the maintenance issue. The code we have must be probably be updated if the TypoRefresh updates. No, please let users complain and nag here instead.

Sounds like the fix for this is removing extra overrides from this form.

Krinkle added a project: Vector (legacy skin).
Krinkle set Security to None.
MarkTraceur claimed this task.

I'm going to close this because the issue is no longer the same, since we shifted to OOUI for all of our text fields. If you still don't like the forms for whatever reason, file another bug explaining why with the new design. Thanks!