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

Add reference to Respond.js' cross-domain proxy, with caveat. #5

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open

Add reference to Respond.js' cross-domain proxy, with caveat. #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -167,10 +167,11 @@ <h1>Other solutions</h1>
</p>
<p>
respond.js is obviously JavaScript dependant, and requires you
to host the CSS on the same server as the page, meaning you
can't use a performance enhancing CDN. Also, I hear it's a little
slow, which JS-CSS crawlers generally are, but I don't have any
evidence particular to respond.js.
to use a slightly complicated
<a href="https://github.com/scottjehl/Respond#cdnx-domain-setup">cross-domain proxy workaround</a>
if you'd like to take advantage of a performance enhancing CDN.
Also, I hear it's a little slow, which JS-CSS crawlers generally
are, but I don't have any evidence particular to respond.js.
</p>
<h1>Won't this bloat my CSS?</h1>
<p>
Expand Down