This isn’t specific to :not(…) and :has(…) selectors- actually, all pseudos in Sizzle allow for quoted arguments. The pattern for pseudos’ arguments is defined as: pseudos = “:(” + characterEncoding + “)(?:\\((?:([‘\”])((?:\\\\.|[^\\\\])*?)\\2|([^()[\\]]*|(?:(?:” + attributes + “)|[^:]|\\\\.)*|.*))\\)|)” Which can be found on line 91 of sizzle.js as of 831c9c48… Let’s add some indentation to that, to … Read more
You can use a combination of the :not and :has selectors like this $(“a.add-span”).click(function() { $(“li:not(:has(span))”).each(function(index) { $(this).append(‘<span class=”spn”>new span<\/span>’); }); }); Here is a demo http://www.jsfiddle.net/xU6fV/
Yes, you can use jQuery selectors on data returned to mutation observer callbacks. See this jsFiddle. Suppose you had HTML like so and you set an observer, like so: var targetNodes = $(“.myclass”); var MutationObserver = window.MutationObserver || window.WebKitMutationObserver; var myObserver = new MutationObserver(mutationHandler); var obsConfig = { childList: true, characterData: true, attributes: true, subtree: … Read more
Just as further reference, and an up-to-date (may’14) (aug’15) (sep’16) (apr’17) (mar’18) (mar’19) (may’20) (jan’22)… Answer that works with: ###Empty strings: If the attr must exist & could have any value (or none at all) jQuery(“[href]”); ###Missing attributes: If attr could exist & if exist, must have some value jQuery(“[href!=”]”); ###Or both: If attr must … Read more
The problem is that brackets have special meaning in CSS (as attribute selectors) and dots do too, as class selectors. Try $.escapeSelector: $(‘#’ + $.escapeSelector(‘Punteggi[@counter].Descrizione’)) This will escape the selector so the special characters don’t affect the selection. You could also try using an attribute selector and wrapping that in quotes: $(‘[id=”Punteggi[@counter].Descrizione”]’) This will literally … Read more
Because of the way the class attribute is designed, you’ll need to make use of at least two other attribute selectors (notice the whitespace in [class*=” detail-“]): $(‘a[class^=”detail-“], a[class*=” detail-“]’); This selects <a> elements with a class attribute that starts with detail-, or contains a class prefixed with detail-. Class names are separated by whitespace … Read more
The reason they are saying: Note: The $(“> elem”, context) selector will be deprecated in a future release. Its usage is thus discouraged in lieu of using alternative selectors. Is due to the comma followed by the context in the selector. E.g. $(“> elem”) is fine however, $(“> elem”, context) will be deprecated. $(“> elem”, … Read more
Reusing the selector reference, your first case, is definitely faster. Here’s a test I made as proof: http://jsperf.com/caching-jquery-selectors The latter case, redefining your selectors, is reported as ~35% slower.
You can create your own selector methods For example, if you want to be able to do the following: $(‘.js-rating-label:hasText(unrated)’); You can define the hasText method as follows $.expr[‘:’][‘hasText’] = function(node, index, props){ return node.innerText.contains(props[3]); } props[3] contains the text inside the brackets after ‘:hasText’.
As you can see from the jsperf test, :not is on average about twice as fast. Overall though this performance will likely be a very small part of your overall execution time. The jquery docs state: The .not() method will end up providing you with more readable selections than pushing complex selectors or variables into … Read more