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

Integrated SalesforceDesignSystemIcons and SalesforceSans? #8

Open
luminixinc opened this issue Apr 10, 2017 · 1 comment
Open

Integrated SalesforceDesignSystemIcons and SalesforceSans? #8

luminixinc opened this issue Apr 10, 2017 · 1 comment

Comments

@luminixinc
Copy link

@jandolina We really like the slick look of the new Salesforce UX icons and the SalesforceSans fonts, thank you!

Here's a feature request :

We would like to get the SalesforceSans-*.ttf font(s) embedded in new version(s) of SalesforceDesignSystemIcons.ttf so that we can render both icon glyphs and "regular" text using a single integrated UI component.

For example we would like to be able to specify a single button/label with the text "\uEBA4 Add", which would be the UtilityAdd icon glyph integrated with the " Add" text). Currently attemping this, and specifying SalesforceDesignSystemIcons.ttf will correctly show the icon glyph, but the text will be rendered in the system default font (tested on Android and Windows); and alternatively specifying SalesforceSans-*.ttf will result in the icon glyph not rendering but the text rendering properly in SalesforceSans.

So currently to achieve this integrated icon/text effect, we need to use two different buttons/labels specifying SalesforceDesignSystemIcons.ttf font family for the icon glyph and SalesforceSans-*.ttf for the regular text. This makes for unnecessarily verbose code when managing the composite UI.

This new feature would be nice to have for the SalesforceSans-*.ttf and SalesforceDesignSystemIcons.ttf fonts across all supported platforms (iOS, Android, Windows, etc).

Kind regards!

@jandolina
Copy link
Contributor

@luminixinc That is an interesting point and good use case. We were keeping the glyphs and icons separate to ensure that there were no character code collisions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants