-
Notifications
You must be signed in to change notification settings - Fork 23
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
Using angular-ui bootstrap components with fonts #22
Comments
I just got done fixing several other issues and don't have time to get to this tonight, but hopefully I'll have time to look at this over the weekend. |
The weird thing is that this error seems to happen on Firefox only, works fine in Chrome. |
I fixed a similar issue this morning with vendorcss not being copied. I'm thinking vendor assets are not copied either. If you're adding that file to the vendor_files:assets variable in the gruntfile, I don't think there's a task setup to actually do anything with it. Look at the one I just closed and see if that's the same scenario, just with assets instead of css - #23. I'm going out of town this weekend, but I will look into it when I get a chance. If you want to tackle it sooner, look at my last commit for the pattern that may lead to your fix - c345109. We just need to do the same thing for assets that I did for css. |
I've been taking a look to this. It seems that out of the box the However, the problem is that the actual 404 is being thrown because vendor assets are copied to the
So, there are 2 solutions that I can think of:
@thardy which one (if any) would be the appropriate one? |
When trying to use the datepicker component from the angular-ui bootstrap library, I got the following errors in Firefox:
How can I link the fonts to my build? I've tried to add the
vendor/bootstrap/dist/fonts*
folder to the assets folder in the Gruntfile but with no success.Is there any particular way of using these components? Can I easily replace these fonts by the one provided by Font Awesome?
The text was updated successfully, but these errors were encountered: