Allow specify font type when declare custom font

[mrtuvn]

Description (*)

Previously custom font can added via theme by less file but some case font use other type (ttf,otf...) magento will not include correctly font. Font will not render properly. This patch allow frontend developers can specific font type when include font in theme.

Use case 1: no define font type -> use default font like before magento will gen font use woff/woff2
Use case 2: use font format -> Developers will need define both format and type for render font

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes Font format incorrect import in theme #29719

Manual testing scenarios (*)

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

Questions or comments

Tested with import Roboto font used ttf format

Before Result: ✖️

Font not found in network chrome devtools

styles-m.css render with font

After Result: ✔️

import

render styles-m.css

web font request

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @mrtuvn. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE,
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

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

⚠️ According to the Magento Contribution requirements, all Pull Requests 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 Pull Requests 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

[edenduong]

@magento run all tests

[magento-engcom-team]

Hi @VladimirZaets, thank you for the review.
ENGCOM-8068 has been created to process this Pull Request
✳️ @VladimirZaets, could you please add one of the following labels to the Pull Request?

Label	Description
Auto-Tests: Covered	All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered	Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required	Changes in Pull Request does not require coverage by auto-tests

[mrtuvn]

@engcom-Alfa @engcom-Bravo @engcom-Kilo can you check this

[mrtuvn]

@magento run all tests

[mrtuvn]

@magento run Functional Tests EE

[engcom-Alfa]

Dev experience is required for testing this PR. Please note that Manual testing has not been performed.

[mrtuvn]

@engcom-Alfa i have updated info manual tests ! Anything missing info here
If you need any info relate for test please let me know

[engcom-Foxtrot]

QA passed.

[m2-assistant]

Hi @mrtuvn, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.