It appears that jQuery selectors are not functioning in the Chrome Console. Any type of selector returns "null". The scripts do properly run the javascript, however.
Has anyone else noticed this change or know of a fix.
Thanks.
Asked
Active
Viewed 9,433 times
17
-
2Can you post examples of code that's not working? – Richard Marskell - Drackir Jan 25 '11 at 16:28
-
1in short, use jQuery in console instead of $ – xster Apr 21 '11 at 14:51
-
at 2012-01-23 accessing jquery via $ is now working in Chrome 16.0 – mozboz Jan 23 '12 at 17:28
2 Answers
17
I uncovered the cause of this in my own question.
The console injects its own function (just a shorthand) for document.getElementById(), aliased to $, which shadows jQuery's $. Easy way to check this: when you're at a breakpoint, and jQuery seems to be broken, compare the following in the console:
jQuery$window.$
The first and last will be jQuery proper, the local $ is something like:
function () {
return document.getElementById.apply(document, arguments)
}
This is because code run from the console is wrapped in a with statement:
with (window ? window.console._commandLineApi : {}) {
with (window) {
// the actual code you typed in here
}
}
and window._commandLineApi.$ is the function that shadows jQuery.
Found the bug in Chromium for this: http://code.google.com/p/chromium/issues/detail?id=70969
-
3or, just type in `jQuery===$`. It will return true if jQuery has control of the $ sign. – Yahel Feb 12 '11 at 04:05
-
1(and, jQuery will return a different looking function, depending on which version of jQuery you're running, so this is easier) – Yahel Feb 12 '11 at 04:05
