I don’t think changing it is a good idea.
Chrome supports it, Firefox support was poor and they had a bug with it, but it also says an improved versio with cache support (finally catching up with chrome) is coming the next version. This can be a couple or months or even less, since this feature is critical.
Its basically a browser change that its breaking things, not the plugin. People that use firefox they understand that browser updates may break things.
Hi Raul,
Thanks for the reply. I totally understand the sentiment behind your decision.
But the problem is that, as it currently stands, this feature is not supported in 3 major versions of Firefox (57,58,59). Firefox 60 is due to be released in May 2018 ( https://wiki.mozilla.org/Release_Management/Calendar ) so there is still around a month till this feature re-lands in Firefox. Also, if you check Bugzilla, there are currently lots of open issues related to preload which are still in works (Refer to https://bugzilla.mozilla.org/buglist.cgi?quicksearch=preload and https://i.imgur.com/jbrTG0o.png )
If possible, is there a way to include a small warning near this option in the plugin informing the users about this feature not being supported in Firefox
Hi Raul,
Sorry for posting in this old thread. Firefox seems to have delayed implementing this even further ( Refer to the thread https://bugzilla.mozilla.org/show_bug.cgi?id=1394778 ). Also, some of the other browsers also don’t support this feature (like old browsers like Internet Explorer and low data browsers like Opera Mini, UC Browser for Android – Refer to https://caniuse.com/#feat=link-rel-preload)
After thinking, changing to a different method for asynchronously loading CSS wouldn’t be required to resolve this issue. If we can add polyfill for rel=preload when this feature is enabled, then that would also resolve this problem. loadCSS has created a polyfill for rel=preload – https://github.com/filamentgroup/loadCSS/blob/master/src/cssrelpreload.js (Compressed version – https://cdnjs.cloudflare.com/ajax/libs/loadCSS/2.0.1/cssrelpreload.min.js )
Sorry for the late reply, but the plugin is already using LoadCSS polyfill.
It’s inlined once you enable async css, but async css loads css files randomly… you need to understand that css files won’t load in order, so you must only have one single css file.
You should probably disable css processing on FVM and then manually dequeue and merge your own css code.
