Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Deprecate jQuery.nodeName, remove in 4.0

See original GitHub issue

Description

jQuery.nodeName is another undocumented utility function that’s exposed on the jQuery object. We should remove it (probably in 4.0 as it’s been there for a long time).

Link to test case

https://jsfiddle.net/o648k3ga/1/

Issue Analytics

State:
Created 7 years ago
Comments:9 (9 by maintainers)

Top GitHub Comments

1reaction

timmywilcommented, Jan 16, 2017

@karan-96 That would be great! You’ll find information on how to contribute here, with info on commits and PRs here. As far as the required work for this issue, that should be all the work needed for jQuery core. We’ll also want to add a warning to the jQuery migrate plugin.

0reactions

dmethvincommented, Jan 23, 2017

@mgol oh sorry, I missed that!

Top Results From Across the Web

Deprecated | jQuery API Documentation

Contains flags for the useragent, read from navigator.userAgent. This property was removed in jQuery 1.9 and is available only through the jQuery.migrate plugin ......

Trigger event when an element is removed from the DOM

There is no built-in event for removing elements, but you can create one by fake-extending jQuery's default remove method. Note that the callback...

Download Diff File - OpenDev

nodeName is deprecated" ); + + migrateWarnFunc( jQuery, "isArray", Array. ... +// behavior is gone in jQuery 4.0 and as it has security...

Blog Home – ThirdLove

But as of jQuery 3.0 (2016), strict mode should be common // enough that all such ... Used for iframes // See setDocument()...

Team:NCTU Formosa/jquery - iGEM 2019

inDisabledFieldset = addCombinator( function (elem) { return elem.disabled === true && elem.nodeName.toLowerCase() === "fieldset"; }, { dir: "parentNode", next: ...