Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

CSS Framework Basics What's New in Foundation 5 New Interchange Features

Problem with foundation 5 project files

Hi guys i'm having a trouble when i'm loading the index file from the project files. It's taking too long to load the page, and when i turn on the js console its says:

Failed to load resource : file://fonts.googleapis.com/css?family=Open+Sans:300italic,400italic,700italic,400,300,700

what can i do to solve this, only happens with chrome. can i delete that line from the foundation.min.css?

"@import url("//fonts.googleapis.com/css?family=Open+Sans:300italic,400italic,700italic,400,300,700");" 

is this line necessary?

2 Answers

So, that line of code is calling in the font "Open Sans" from Google's font library. Looking at a similar issue to this on Zurb's forum, it looks like the problem is likely that you are developing locally so the relative link you are calling in the import url is defaulting to "file://" instead of http://.

You should be able to get it to work locally if you add http: or https to make it an absolute link as below:

"@import url("http://fonts.googleapis.com/css?family=Open+Sans:300italic,400italic,700italic,400,300,700");"

Alternately if you are using the Sass version of Foundation and don't want to use Open Sans, you can change $include-open-sans in _global.scss from true to false.

Using custom fonts does add to page-load time, but if this is the only one you are loading it shouldn't make a huge impact.

i understand , the problem is beacuse im working them locally? so when i do this at a server shouldnt happen this on chrome... well that's fine, thanks michael

You're welcome, glad I could help :)

Yes, you should be fine once you are on a live server if I understand the problem correctly.