Font format incorrect import in theme

[mrtuvn]

Preconditions:

Magento 2.4-develop

Default magento font import lib-font-face use type woff or woff2. In real case when user use another font type such as true type. Font import will work incorrect if add format truetype

Example in less define custom font

.lib-font-face( @family-name: 'Inter-Light', @font-path: '@{baseDir}fonts/Inter-Light', @font-format: 'ttf', @font-weight: normal, @font-style: normal, @font-display: auto );

will generate css font-face

@font-face { font-family: 'Inter-Light'; src: url('../fonts/Inter-Light.ttf') format('ttf'); font-weight: normal; font-style: normal; font-display: auto; }
format font src seem incorrect in the case truetype. Reference in this doc

https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face

src: url('../fonts/Inter-Light.ttf') format('ttf') should be

src: url('../fonts/Inter-Light.ttf') format('truetype');

Steps to Reproduce:

1. Tested with font added with /web/css/source/_typography.less inside luma/blank theme or custom theme
2. Use custom font non-default from magento (ttf, eot)
3. use format specific while import font
4. Also use type font specific too
5. Make sure output css render and page load without problem. Font render correctly

Actual Result: ✖️

Font not render properly

styles-m.css render with font

Expected Result: ✔️

import

render styles-m.css

web font request

Proposed solution

--- Update mixin font with new type font argument in order import correct type
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users with no workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @mrtuvn. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[harold-tech]

I.still don't know what I'm doing but I will work until I know but me an Ci have a date and its no rush

[magento-engcom-team]

✅ Confirmed by @engcom-Alfa
Thank you for verifying the issue. Based on the provided information internal tickets MC-38231 were created

Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[magento-engcom-team]

Hi @mrtuvn. Thank you for your report.
The issue has been fixed in #29726 by @mrtuvn in 2.4-develop branch
Related commit(s):

• 9e48f91c7f3e67b8d49195fd2f6a3b3e03bc7025

The fix will be available with the upcoming 2.4.2 release.