Google Fonts break

hmm .. that should actually already be happening as per the code in https://github.com/futtta/autoptimize/blob/master/classes/autoptimizeStyles.php#L234-L280

can you share the URL to your site for me to have a look at, so I might see why this does not work in your case?

frank

Hi Frank,
sure thing – check out https://feelinghands.at/

Michael

thanks Michael; I can confirm this is a bug, I hope to have a fix for this tomorrow.

frank

Hi Michael;
This should be fixed on the development version.

Can you download the zip-file from GitHub and overwrite your wp-content/plugins/autoptimize with the contents of autoptimize-master in the zip-file and let me know if this indeed fixes things for you?

frank

Hi Frank,
now it is in the beginning and working fine.
What I don’t understand is that I could not replicate the font-issue this morning, so my browser was loading them… very weird.

Thanks,
Michael

great, thanks for confirming! ??

There’s an exception to this rule.

@charset (if present) should appear before @import.

https://developer.mozilla.org/en/docs/Web/CSS/@import

Possibly a YUI compressor bug?

that’s an interesting remark @superpoincare; AO currently does specifically handle @charset (nothing to do with YUI, but AO itself). taking into account that multiple original CSS-files might have different character encodings, it might prove difficult to support that correctly as well. have you encountered problems due to this already?

frank

No I haven’t encountered any problem Frank. My comment was just an alert on the rule … just in case.