Closed GoogleCodeExporter closed 9 years ago
We already do have a fixed order of filters, and filters optimizing each
other's output (for many things it's actually a partial order in a dependency
graph).
In some cases it's purposefully different from what you list, though. For
example we always run combine_css before rewrite_css as that produces much
smaller URLs (but javascript optimization always runs before its combiner
because we won't be able to optimize the JS combiner output).
Original comment by morlov...@google.com
on 26 Jun 2013 at 1:37
Actually, after posting this, I've been doing more experimentation and was
coming to this conclusion. However, I've been trawling trying to find the order
of precedence/dependencies through the documentation. Do you have a link?
Original comment by shri...@gmail.com
on 26 Jun 2013 at 1:41
Only a code one. Basically the order of filters is based on how
RewriteDriver::AddFilters adds them.
Original comment by morlov...@google.com
on 26 Jun 2013 at 1:52
Actually the order is supposed to be accurate in
https://developers.google.com/speed/pagespeed/module/config_filters
Note the text "The order of the directives in the configuration file is not
important: the rewriters are run in the pre-defined order presented in the
table:"
However, there is no mechanical enforcement of this as we add filters & update
doc, so it's possible we blew it.
Original comment by jmara...@google.com
on 26 Jun 2013 at 2:05
I'm terribly sorry, I missed that line entirely.
Original comment by shri...@gmail.com
on 26 Jun 2013 at 2:10
Original comment by sligocki@google.com
on 26 Jun 2013 at 3:30
Original issue reported on code.google.com by
shri...@gmail.com
on 26 Jun 2013 at 11:46