Joy
(@joyously)
I searched and read thru many posts but have did not see this declared on any schedule or roadmap. Looked like in some threads a method for removing it but I didn’t see any definitive. How do I eliminate Google seeing it might be the better question. thanks
Joy
(@joyously)
Well, according to this https://developer.wordpress.org/reference/functions/wp_deregister_script/ you can’t deregister it. I would have suggested that, because in order to register a replacement, you have to deregister the original.
So that leaves filtering the URL itself to point to a different version than what is bundled with WP. See https://developer.wordpress.org/reference/hooks/script_loader_src/
That makes sense. Thank you for your answer. So, there is possible workaround but there is no formal plan by WordPress to integrate a fix.
Maybe I will try the plugin solution though that makes me nervous.
http://www.ramoonus.nl/wordpress/jquery-updater/
Joy
(@joyously)
Hey, I never said “there is no formal plan by WordPress to integrate a fix”!
There are tickets to update jQuery, but it requires a lot of testing. I have brought it up in the Slack core dev chat, and so have other people. It just hasn’t happened yet.
Joy
(@joyously)
I just added it to the list for consideration in 5.3.
WP5.3: Open Call for Tickets
Joy
(@joyously)
I just saw that this ticket is going into 5.2.1
https://core.trac.wordpress.org/ticket/47020
That’s pretty cool. You are a helpful person Joy! I’ll try that plugin on some sites and see if Google gets fooled. Lighthouse did not used to report those things but it recently began to I think.
Craig
