Skip to content

Conversation

@mmalerba
Copy link
Contributor

No description provided.

…o 2018 typography

This PR cleans up some typography hacks in menu and table in favor of a
higher level fix in the mapping code itself. Despite the naming
subheading-1 in the 2014 system looks more like body-1 in the 2018 system
and body-2 in the 2014 system looks more like subtitle-2 in the 2018
system. See my hackmd for the original typography mapping plan for a
side-by-side comparison of the different levels & systems:
https://hackmd.io/-IBynZC1QHCBefcFQyaAkA
@mmalerba mmalerba added P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful G This is is related to a Google internal issue target: patch This PR is targeted for the next patch release labels Sep 22, 2021
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 22, 2021
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mmalerba mmalerba added the action: merge The PR is ready for merge by the caretaker label Sep 22, 2021
@amysorto amysorto merged commit c649f7d into angular:master Sep 24, 2021
amysorto pushed a commit that referenced this pull request Sep 24, 2021
…o 2018 typography (#23618)

* fix(material-experimental/mdc-menu): fix bold font when using 2014 typography

* fix(material-experimental/mdc-typography): better mappings for 2014 to 2018 typography

This PR cleans up some typography hacks in menu and table in favor of a
higher level fix in the mapping code itself. Despite the naming
subheading-1 in the 2014 system looks more like body-1 in the 2018 system
and body-2 in the 2014 system looks more like subtitle-2 in the 2018
system. See my hackmd for the original typography mapping plan for a
side-by-side comparison of the different levels & systems:
https://hackmd.io/-IBynZC1QHCBefcFQyaAkA

(cherry picked from commit c649f7d)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Oct 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement G This is is related to a Google internal issue P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants