Warning: event.returnValue deprecated; use standard event.preventDefault()

ronherren
(@ronherren)

10 years, 1 month ago
I am running 3.8.1 clean install and Customizr theme, and the only issue Chrome developer tools reports, during page load, is the following warning:

event.returnValue is deprecated. Please use the standard event.preventDefault() instead. jquery.js?ver=1.10.2:4

If it helps narrow-down root cause the following threads point to register_sidebar as possibly linked to this warning:

Event_Organiser Calendar Next and Prev links not working
Event Organiser FAQ

FYI, I am not using “Event Organiser.” I only mention these because I recall implementing a register_sidebar based upon this Customizr code snippet, and it appears to be possibly incomplete? Not sure; grasping at a few straws here… the before_ and after_ are empty; is this ok?
```
if (function_exists('register_sidebar')) {
    register_sidebar(array(
        'name' => 'Extra Widget In Socials',
        'id' => 'extra-newsletter-widget',
        'description' => 'Extra widget in the social links area',
        'before_widget' => '',
        'after_widget' => '',
        'before_title' => '',
        'after_title' => ''
    ));
}
```

Viewing 8 replies - 1 through 8 (of 8 total)

ElectricFeet
(@electricfeet)

10 years, 1 month ago

Well I wrote that snippet and can confidently say, “I don’t know” 🙂

In other situations, I’ve seen the “before” and “after” contain things like <div> and <h2>, which I knew I didn’t need in this case.

I’m happy to correct the snippet if you can tell me what needs to change.

Thanks!

marnixbras
(@marnixbras)

10 years, 1 month ago

Same problem here. Some rendering issues in the Ubermenu plugin .

also errorwarning ” event.returnValue is deprecated. Please use the standard event.preventDefault() instead. jquery.js?ver=1.10.2:4 “

this pointed to /wp-includes/js/jquery/jquery.js

I replaced te content of /wp-includes/js/jquery/jquery.js with http://code.jquery.com/jquery-1.11.0.min.js

(So I upgrades Jquery from 1.10.2 to 1.11.0 manually ) : problem solved

Rocco Aliberti
(@d4z_c0nf)

10 years, 1 month ago

so… wp “issue”

marnixbras
(@marnixbras)

10 years, 1 month ago

Do you know where to address this issue? so it can be fixed in the next release op WP?

Rocco Aliberti
(@d4z_c0nf)

10 years, 1 month ago

sorry I forgot the question mark 😀
it should be
“so wp issue?”

Rocco Aliberti
(@d4z_c0nf)

10 years, 1 month ago

I tried to “hide” some js, and looks like that customizr bootstrap.min.js and modernizer.min.js cause that warning.
But.. what kind of real problem it cause?
It’s just a deprecation warning, not an error..

Anyway going in the dashboard, also hiding all customizr js, I get that warning, so it’s a common “issue” at least.

ElectricFeet
(@electricfeet)

10 years, 1 month ago

This looks like a good answer:

This is a warning related to the fact that most JavaScript frameworks (jQuery, Angular, YUI, Bootstrap…) offer backward support for old-nasty-most-hated Internet Explorer starting from IE8 down to IE6 :/

One day that backward compatibility support will be dropped (for IE8/7/6 since IE9 deals with it), and you will no more see this warning (and other IEish bugs)..

It’s a question of time (now IE8 has 10% worldwide share, once it reaches 1% it is DEAD), meanwhile, just ignore the warning and stay zen 🙂

So this is nothing to do with Event Organiser, nor WordPress, but related to the fact that the underlying Twitter Bootstrap—used by Customizr—supports IE8. Chrome is warning you that it will—one day, probably well after IE8 has shuffled off this mortal coil—drop support for it.

(And, by the way, this is the reason for a lot of the other browser warnings: supporting IE8 inevitably introduces non-standard hacks, because IE8 itself was one big non-standard hack.)

By the time Chrome drops support, you’ll be running a much later version of Customizr and WordPress and won’t need to worry about it.

xandrucancelas
(@xandrucancelas)

10 years ago

We are creating a plugin to disable the GA cookies (clearing it) and the function clear all GA cache values, but at the last executing of jquery we have the same problem and the cookies have again a value again :s

It’s strange because it happens if the script is inside the plugin, if it’s called to external it works fine.

Best regards