Support » Plugin: HTML Forms » Error in public.js in Chrome 41 –used by Googlebot web rendering service (WRS)–

  • Resolved diegocanal



    Currently (January 2019) Googlebot uses a web rendering service (WRS) that is based on Chrome 41 (M41), so even being an outdated browser it’s important to make sure everything works OK and that we don’t get any errors in it. As Google engineers state:

    In addition to using feature detection and polyfills, be sure to collect and analyze client-side errors that may prevent your application from behaving correctly when accessed by users and Googlebot.

    Testing HTML Forms in Chrome 41.0.2272.0 (64-bit) for Mac OS X I get an error in the console related to the file /assets/js/public.js:

    Uncaught ReferenceError: URLSearchParams is not definedpublic.js:216 (anonymous function)public.js:265 3.i.initpublic.js:425 5../conditionality.jspublic.js:1 lpublic.js:1 opublic.js:1 (anonymous function)public.js:1 (anonymous function)

    It might be related to the fact that the Googlebot WRS does not support ES6. Google engineeers recomend:

    Chrome M41 does not support ES6 features (for example classes). If you are using ES6 make sure to transpile your JavaScript to ES5.


Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Lap


    I am not 100% sure if this error is really related to HTML Forms, but I will forward this information to Danny. Thank you!



    I am not 100% sure if this error is really related to HTML Forms

    Why do you say so?

    FYI, I’ve properly tested it using Twenty Sixteen with no plugins at all apart from HTML Forms. Here you have a link and a screenshot showing the error message —which as you can see is pointing to the file /plugins/html-forms/assets/js/public.js:216—:

    • This reply was modified 4 months ago by  diegocanal.
    Plugin Contributor Lap


    Thank you, Danny is informed and looking into the issue.

    Plugin Contributor Lap


    We forgot to mention it here, but the issue has been solved. Thanks for letting us know about the error!

    Hi Lap!

    Thanks for keeping me posted.

    I didn’t see this fix on the changelog, nor any related issue at GitHub’s repo. Would it be too much if I ask about what was the actual problem?

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.