- Do we want the “chrome” of the skin to respond to font size options, or just certain things like the article and potentially talk page text?
- Depending on this answer, we will need to support not only 14px and 16px body font sizes, but also more sizes (like 18px or 20px).
- Should we have all size modes on all skins?
- What factors affect the "default" behavior of the system? What if different wikis configure different defaults for each skin?
- Should the “chrome” be sized to the default option?
- What about other use cases which don’t have font size options, like Wikifunctions?
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • Sarai-WMDE | T322383 TypeaheadSearch line-height, thumbnail size don't match Figma spec or each other | |||
| Open | None | T322384 Increase MenuItem / TypeaheadSearch line-height | |||
| Stalled | None | T372653 Font size setting should apply consistently across mobile and desktop | |||
| Open | BUG REPORT | None | T387983 Select dropdown for the "Reason" field in Codex Special:Block has text not in the center of the element | ||
| Resolved | DTorsani-WMF | T363845 [EPIC] Typography scale and font sizing | |||
| Resolved | DTorsani-WMF | T363848 Resolve open questions surrounding expected compatibility of different size "modes" within Codex |
Event Timeline
Comment Actions
Answering these questions at this point after conversations on DST:
- Do we want the “chrome” of the skin to respond to font size options, or just certain things like the article and potentially talk page text?
- Depending on this answer, we will need to support not only 14px and 16px body font sizes, but also more sizes (like 18px or 20px).
For an MVP, we will prioritize Codex font modes of 14px and 16px, to support the "chrome" for environments which use these body font sizes in the chrome historically, i.e. Vector (14) and MinervaNeue (16).
- Should we have all size modes on all skins?
The new and improved Codex type scale would support all font size modes in all skins, should the Web team choose to implement that, but for components the elements in the "chrome" we will only focus on 14 and 16, as mentioned above.
- What factors affect the "default" behavior of the system? What if different wikis configure different defaults for each skin?
- Should the “chrome” be sized to the default option?
The Codex font mode being used in the "chrome" for each different wiki would depend on the body font size of the "chrome" for that wiki.
- What about other use cases which don’t have font size options, like Wikifunctions?
I would imagine these environments would determine which font mode they want to use overall.