You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this in relation to an existing part of Font Awesome or something new?
This offers a variant of alternative techniques already available.
What is 1 thing that we can do when building this feature that will guarantee that it is awesome?
Authors who chose this option would need to maintain only a single (CSS) file.
Why would other Font Awesome users care about this?
Since authors are moving away from font files for decorative symbols, an SVG-in-CSS solution that uses basically the same markup authors are used to, should look attractive to them. They could easily delete lines for icons they do not need from the single file they had to maintain.
Feature request checklist
This is a single feature
The title starts with "Feature request: " and is followed by a clear feature name
You are already providing SVG symbols (and paths) embedded in JS, JSON and YAML, but not in a single CSS file via
data
scheme URLs.Related: #3203, #14279, #10352
Is this in relation to an existing part of Font Awesome or something new?
This offers a variant of alternative techniques already available.
What is 1 thing that we can do when building this feature that will guarantee that it is awesome?
Authors who chose this option would need to maintain only a single (CSS) file.
Why would other Font Awesome users care about this?
Since authors are moving away from font files for decorative symbols, an SVG-in-CSS solution that uses basically the same markup authors are used to, should look attractive to them. They could easily delete lines for icons they do not need from the single file they had to maintain.
Feature request checklist
The text was updated successfully, but these errors were encountered: