You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use a cache buster variable to force the loading of new CSS. The respond-proxy.html file has a faulty regex that expects .css to be the last part of the string.
We had a similar issue with compressed assets. Our are .css.gz, sometimes. For now we just hacked the code in the HTML, but maybe there's a cleaner solution?
We use a cache buster variable to force the loading of new CSS. The respond-proxy.html file has a faulty regex that expects .css to be the last part of the string.
E.g., the stylesheet:
http://www.example.com/style.css?1234
Will attempt to load cross domain, using:
http://cdn.example.com/proxy/respond-proxy.html?url=http://www.example.com/respond.proxy.gif&css=http://www.example.com/style.css?1234
Notice the double question marks.
The text was updated successfully, but these errors were encountered: