Install autoprefixer #81
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR makes 2 changes:
buildscript to add browser prefixes to css where needed.--> still a question if this is the best solution, there's a ticket to discuss this here: How to deal with browser prefixes in USWDS #80
lib/fontsdirectory and create a new version of the font-faces file from VA's design system in order to change the path of the font. This path was failing because we don't redirect the fonts to the base path, like vets-website does. I created a comment in this issue to further look into this: Discovery on best way to import USWDS images and fonts #66.