-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Addition of more then one Font Family for Typography Theming #5563
Comments
jelbourn
added
discussion
feature
This issue represents a new feature or feature request rather than a bug or bug fix
labels
Jul 7, 2017
@crisbeto thoughts? |
It definitely makes sense. It shouldn't be too much trouble to support since it can fall back to the main font family. |
jelbourn
added
P4
A relatively minor issue that is not relevant to core functions
and removed
discussion
labels
Jul 7, 2017
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jul 20, 2017
Allows for the `font-family` to be overwritten on a per-level basis. The default one is still taken from the base config. Fixes angular#5563.
crisbeto
added a commit
to crisbeto/material2
that referenced
this issue
Jul 20, 2017
Allows for the `font-family` to be overwritten on a per-level basis. The default one is still taken from the base config. Fixes angular#5563.
kara
pushed a commit
that referenced
this issue
Jul 20, 2017
Allows for the `font-family` to be overwritten on a per-level basis. The default one is still taken from the base config. Fixes #5563.
kara
pushed a commit
that referenced
this issue
Jul 21, 2017
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug, feature request, or proposal:
Feature
What is the current behavior?
Typography theming allows a single font-family to be chosen using $font-family in the configuration
What is the use-case or motivation for changing an existing behavior?
Most applications and sites use more then one font-family. Typically h1 and/or h2 ($title) headers use a second font-family, but other then creating a second config there's no way to override the $title with a second font-family. Something like mat-typography-level taking another parameter to override the font-family, or an new mixin that does both level and font-family so the mixin name more closely reflects it's use.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 4.2.5, Angular Material 2.0.0-beta.7, Windows 10
The text was updated successfully, but these errors were encountered: