Cannot read property "checkImageForCriticality" of Undefined

35 views
Skip to first unread message

Danny Michel

unread,
Feb 25, 2017, 10:35:07 AM2/25/17
to ngx-pagespeed-discuss
I get this error when refreshing.
Thanks in advance for any help.

Otto van der Schaaf

unread,
Feb 25, 2017, 10:42:30 AM2/25/17
to ngx-pagespeed-discuss

That sounds a bit like https://github.com/pagespeed/mod_pagespeed/issues/1281
Does the page that you refresh depend on JavaScript for loading html?

Otto


On Sat, Feb 25, 2017, 16:35 Danny Michel <danield...@gmail.com> wrote:
I get this error when refreshing.
Thanks in advance for any help.

--
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-di...@googlegroups.com.
Visit this group at https://groups.google.com/group/ngx-pagespeed-discuss.
For more options, visit https://groups.google.com/d/optout.

Danny Michel

unread,
Feb 25, 2017, 10:53:46 AM2/25/17
to ngx-pagesp...@googlegroups.com
Yes, the page i’m loading does depend on javascript
I saw that issue but was unsure what he meant to do
Is he saying to add
location /xhr {
ModPagespeedDisableFilters prioritize_critical_css;
}
to my server block?
I’m not exactly sure what this has to do with CSS

Danny Michel

unread,
Feb 25, 2017, 10:55:22 AM2/25/17
to ngx-pagespeed-discuss
I mean 


location /xhr {

       pagespeed DisableFilters prioritize_critical_css;

Otto van der Schaaf

unread,
Feb 25, 2017, 11:27:05 AM2/25/17
to ngx-pagespeed-discuss

If you have javascript running on your page which loads a html fragment from, say, /ajaxhtmlfragment, you should probably disable the prioritize_critical_css filter for /ajaxhtmlfragment. Doing so would allow you to avoid getting the js error that you are seeing.

Otto

--

Danny Michel

unread,
Feb 25, 2017, 3:43:14 PM2/25/17
to ngx-pagespeed-discuss
thank you


On Saturday, February 25, 2017 at 11:27:05 AM UTC-5, Otto van der Schaaf wrote:

If you have javascript running on your page which loads a html fragment from, say, /ajaxhtmlfragment, you should probably disable the prioritize_critical_css filter for /ajaxhtmlfragment. Doing so would allow you to avoid getting the js error that you are seeing.

Otto

On Sat, Feb 25, 2017 at 4:55 PM Danny Michel <danield...@gmail.com> wrote:
I mean 


location /xhr {

       pagespeed DisableFilters prioritize_critical_css;

}



On Saturday, February 25, 2017 at 10:35:07 AM UTC-5, Danny Michel wrote:
I get this error when refreshing.
Thanks in advance for any help.

--
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-discuss+unsub...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages