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 has been archived by the owner on Apr 21, 2023. It is now read-only.
Using the latest development version of mod_pagespeed, if you place some
javascript within an IE comment block, it is ignored by the defer_javascript
filter.
This can cause issues where it is reliant on various javascripts having been
loaded previously.
If the code is not within an IE comment block, it gets deferred as you would
expect and there are no problems.
Original issue reported on code.google.com by rwap.services on 8 Jan 2013 at 10:27
OK it's starting to look like fixing Issue 553 properly is more compelling.
Earlier we were thinking it was simply that we were missing out on
optimizations. But breaking pages is not great.
One thing we can do with our current infrastructure is defer all scripts prior
to the IE directive until the IE directive. Then start again after the IE
directive. That way we preserve overall order.
I'm CCing Kishore so he is conscious of this but I think we should solve Issue
553 first.
Original comment by jmara...@google.com on 8 Jan 2013 at 1:31
Original issue reported on code.google.com by
rwap.services
on 8 Jan 2013 at 10:27The text was updated successfully, but these errors were encountered: