Skip to main content

Pseduo-RegEx JQuery Selectors

More often than not I find myself using only few jQuery selectors to locate elements in DOM for event binding; however, jQuery also offers some powerful psedo-RegEx selectors for locating elements.

Say, you have the following HTML5 markup:

--------------------------------------------------
<!DOCTYPE HTML>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <title>JQuery Selector</title>
</head>
<body>
    <article class="post-article">
        <header class="article-header"></header>
        <p class="article-content"></p>
    </article>
</body>
</html>
--------------------------------------------------

You can use the following selectors to locate the "article-header" element.

1- Using closest 
   $(".post-article").closest("header").first()

2- If DOM is properly ordered
 $(".post-article").firstChild()

3- Using psedo-RegEx expressions
The general parttern for using psedo-RegEx expressions is as follows:

$("[atttr{selectorExpression}{selectorText}]")

Where:

attr - Is the attribute of the DOM element (e.g class, id, style, name, etc...)
selectorExpression - Is the RegEx expression (e.g. ^ for starts with, ~ for contains, ! for not)
selectorText - is the text that is used in the DOM element

Using the example above:

To select the "article-header" element you can use the "equals to" selector as follows:

$("[class=article-header]")

or if the class name starts with "article-header," you can use the "starts with" operator as follows:

$("[class^=article-header]") or  $("[class~=article-header]") for contains operator.

Alternatively, if you are only interested in elements other than the "article-header" element. You can use the "not" operator as follows.

$("[class!=article-header]")

Here is a complete list of jQuery selectors:









Comments

Popular posts from this blog

Turning WCF Service into .asmx for debugging

Even though .asmx web services are becoming dinosaurs of the new .NET world of WCF. I missed the simplicity of debugging code right in visual studio without: Creating a client to consume WCF service Attaching w3p.exe process and Adding break points  One quick solution: Turn WCF service into .asmx service with few lines of code, debug your code with asmx, and turn .asmx off during deployment.  Detail steps: 1- First take your WCF class and add WebService attribute to it Code Snippet /// <summary> /// Dual mode with .ASMX and WCF /// </summary> [ WebService (Namespace = "http://www.yourdomain.com/" )] 2- Then add WebMethod attribute to a function you want to expose in .asmx Code Snippet [ WebMethod ] public List < PageController . Page > DualFunction() { 3- Take the .svc file from your solution - copy and rename the copied file [YourOriginalWCFFile.asmx]. Open up the copied file and rename "ServiceHost&qu

ASP.MVC Real-time data processing with Sharded RavenDB and SignalR

In a move that some call "Radical” The Weather Channel recently swapped their enterprise Oracle and MySql Databases for NoSQL  MongoDB .  One word that could describe the rapid adoption of NoSQL databases compared to relational once is “ sharding .” Unlike relational databases, NoSQL systems allow developers to be active participants in the data storage process by providing a way to create logic (sharding strategy) that outlines how and where data could be stored, resulting in better scalability and improved performance. RavenDB , an open source NoSQL system for .NET that is easy to deploy (both as a standalone/embedded system) for an ASP.MVC application. SingalR is a tool that one can use in a .NET environment to add real-time client-server processing in an application. SignalR allows a developer to broadcast messages to all (or some) clients from a centralized client and/or server call. I was looking for a quick data-sharding example with embedded RavenDB that I can

Processing ASP MVC Web API Requests in Multi-threaded JS Web Worker

Unlike an asynchronous Ajax call, HTML5 Web workers provide an opportunity to run a Multi-threaded JavaScript code in modern browsers that support them . Each worker spawns an isolated thread with dedicated JavaScript Event Loop, Stack and Heap memory. For example a regular Ajax Call to MVC Web API service call goes through the following asynchronous call cycle. The JavaScript Event Loop in this case could be interrupted by events that are being executed on the UI; for instance, a "window.alert", could possibly stop all scripts on the page from executing until a user responds. Replacing the Ajax Call with HTML5 web worker provides a great way to run long running scripts in separate threads so that asynchronous code execution is not interrupted by UI events. Here is the a JavaScript worker implementation of the same MVC Web API call using a JavaScript web worker. Despite the advantages of using a web worker, implementing one requires working with some constr