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
When using stylesheet_link_tag in Rails, it also inserts a Link: <my_stylesheet.css>; rel=preload; as=style header in the response.
This is also sent in the responses to Turbo navigations. In Chrome, this seems to trigger re-fetching the stylesheet (albeit from local cache), which then complains a few seconds later to console:
The resource http://192.168.86.25:3000/packs/css/application.css was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.
I can avoid the issue if I change my stylesheet tags to something like
Think this is a dumb Chrome bug that we should just ignore? Or should turbo-rails be automatically suppressing Link headers to avoid the redundant asset load?
The text was updated successfully, but these errors were encountered:
When using stylesheet_link_tag in Rails, it also inserts a
Link: <my_stylesheet.css>; rel=preload; as=style
header in the response.This is also sent in the responses to Turbo navigations. In Chrome, this seems to trigger re-fetching the stylesheet (albeit from local cache), which then complains a few seconds later to console:
I can avoid the issue if I change my stylesheet tags to something like
to avoid the Link header on turbo navigation.
Think this is a dumb Chrome bug that we should just ignore? Or should turbo-rails be automatically suppressing Link headers to avoid the redundant asset load?
The text was updated successfully, but these errors were encountered: