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.

Sign up for GitHub

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

Jump to bottom

Support relative paths to static assets #83

Closed
mbeard opened this issue Nov 2, 2015 · 2 comments
Closed

Support relative paths to static assets #83

mbeard opened this issue Nov 2, 2015 · 2 comments
Assignees
@kaelig
Labels
bug

Comments

@mbeard
Copy link

mbeard commented Nov 2, 2015

Currently, the compiled CSS salesforce-lightning-design-system.css assumes that static files (icons, fonts, images) reside under an /assets directory.

Can these references be updated to relative paths instead of absolute paths to allow more flexibility in how these files are hosted in consuming apps.

For example
src: url("../fonts/webfonts/SalesforceSans-Light.woff2")

instead of
src: url("/assets/fonts/webfonts/SalesforceSans-Light.woff2")
@cosminnicula
Copy link

+1

@BenjaminNeilDavis BenjaminNeilDavis mentioned this issue Nov 12, 2015
Closed
brandonferrua added a commit that referenced this issue Nov 18, 2015
@brandonferrua
Merge pull request #83 from salesforce-ux/links-typo
f390254 
change title to articles
@rickschmoo rickschmoo added this to the 03/16 milestone Feb 4, 2016
@rickschmoo rickschmoo assigned kaelig and unassigned rickschmoo Feb 4, 2016
@kaelig kaelig closed this as completed Mar 8, 2016
@kaelig
Copy link
Contributor

kaelig commented Apr 9, 2016

Thank you for your patience, this was just fixed in the latest version of the Lightning Design System!

See full release notes: https://www.lightningdesignsystem.com/release-notes/

@bensleveritt bensleveritt mentioned this issue Oct 12, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kaelig kaelig

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kaelig @rickschmoo @mbeard @cosminnicula