Skip to content
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

feat(typography): use variable fonts instead of statics one by default #30328

Open
MikaStark opened this issue Jan 14, 2025 · 1 comment
Open
Labels
area: material/core docs This issue is related to documentation feature This issue represents a new feature or feature request rather than a bug or bug fix P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@MikaStark
Copy link

MikaStark commented Jan 14, 2025

Feature Description

Hi 🙌
I propose replacing the current static fonts for Roboto and Material Symbols with their variable font counterparts.

It will bring minor but valuable improvements especially for newcomers :

  • Reduced file sizes and HTTP requests.
  • Greater control over font properties (e.g., weight, width).
  • Aligns with the latest web standards.

This change would enhance Angular Material’s efficiency, design capabilities, and relevance.

Here is a quick example of new default font import proposal :

<link rel="preconnect" href="https://fonts.googleapis.com" />
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
<link
  href="https://fonts.googleapis.com/css2?family=Roboto:ital,wght@0,100..900;1,100..900&display=swap"
  rel="stylesheet"
/>
<link
  rel="stylesheet"
  href="https://fonts.googleapis.com/css2?family=Roboto:ital,wdth,wght@0,75..100,100..900;1,75..100,100..900&display=swap"
/>

Thank you for considering this request.

Use Case

  • Enhance getting started with Angular Material experience
  • Promote modern font technologies
  • Align with latest web standards
  • Better maintenability and performance
@MikaStark MikaStark added feature This issue represents a new feature or feature request rather than a bug or bug fix needs triage This issue needs to be triaged by the team labels Jan 14, 2025
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent docs This issue is related to documentation area: material/core and removed needs triage This issue needs to be triaged by the team labels Jan 21, 2025
@Sepandard
Copy link
Contributor

Sepandard commented Jan 25, 2025

Hi, I started working on this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: material/core docs This issue is related to documentation feature This issue represents a new feature or feature request rather than a bug or bug fix P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

No branches or pull requests

3 participants