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
{{ message }}
This repository was archived by the owner on Apr 10, 2025. It is now read-only.
Thanks for the report. For quick workaround, I suggest using ModPagespeedDisallow to avoid processing the CSS file with the unicode characters. Hopefully this (a) doesn't affect all of them and (b) maybe you could split it just the rules that have this.
I'll check into what the status of this is. A few things are fixed in 1.12 (that's now stable) however this one doesn't ring a bell.
ashishk-1
added a commit
to ashishk-1/incubator-pagespeed-mod
that referenced
this issue
Aug 11, 2017
What steps will reproduce the problem?
unicode-range
CSS declaration in a stylesheet:unicode-range: U+0400-045F, U+0490-0491, U+04B0-04B1, U+2116
What is the expected output?
unicode-range:U+0400-045F, U+0490-0491, U+04B0-04B1, U+2116
What do you see instead?
The CSS minification output breaks the value, placing a space between the 'U' and '+':
unicode-range:U +0400-045F , U +0490-0491 , U +04B0-04B1 , U +2116
This prevents the browser from seeing the proper value, therefore always downloading the font even if the intended range of characters is not used.
What version of the product are you using?
X-Mod-Pagespeed: 1.11.33.4-0
Which OS? Which version of Apache? Which MPM?
CentOS, Apache/2.2.27 (prefork)
The text was updated successfully, but these errors were encountered: