Open janslu opened 6 years ago
That looks similar to what https://github.com/apache/incubator-pagespeed-mod/commit/2fb25bc323ebabf14eb0072dfa5574c432a30b86 fixed. Is the ngx_pagespeed version involved the latest one? (1.13.34.2?)
Yes, this seems like similar issue but I'm on the latest stable 1.13.35.2.
Sounds like a separate issue then, thanks for the report. I think that either completely disabling css rewriting [1] or excluding [2] the offending css url will help short term.
[1] https://www.modpagespeed.com/doc/filter-css-rewrite [2] https://www.modpagespeed.com/doc/restricting_urls
Disabling css_rewrite wasn't enough, I had to disable combine_css also. Thanks for taking a look into this. I wish IE could be forgotten already...
Hi @janslu How about disable it for the implied user-agent? I don't know the apache exacts syntax, but some like If UA like "explorer" then pagespeed DisableFilter combine_css;
@Lofesa Haven't thought about it... I don't know if it's even possible because I'm also using nginx to cache and store the page output. I'll look into it.
if ($http_user_agent ~* "^xxx$") { pagespeed DisableFilter combine_css; } where xxx is the user-agent string.
I have a problem with a large css file generated by one of the frameworks. Current ModPagespeed built on nginx 1.14 rewrites one of the rules from:
to
This change is fine in most browsers, but breaks Internet Explorer 11. Unfortunately this rule is used for a main site grid and the whole layout breaks. I have tried to find a place to disable this change, but I couldn't. Here are my enabled filters:
Any idea how I can protect this part of css from "optimization"?