https://stackoverflow.com/questions/7238586/do-i-need-to-be-concerned-with-race-conditions-with-asynchronous-javascript/7238663#7238663
https://stackoverflow.com/questions/7868434/are-calls-to-javascript-methods-thread-safe-or-synchronized/7868445#7868445
https://stackoverflow.com/questions/7575589/how-does-javascript-handle-ajax-responses-in-the-background/7575649#7575649
Oct 18, 2017
Aug 30, 2017
XSLT - basics, tips & tricks
This post is created from Pluralsight video:
XSLT 2.0 and 1.0 Foundations by Dimitre Novatchev
You can "develop" XSLT in Visual Studio. Create or open XSLT as simple file and execute Start debugging from Debug menu.
You can't learn XSLT without XPath.
XSLT is built around concept of templates.
XSLT can use one or even more XML as input data. Templates can be viewed as peace of code that must target using XPath some elements of XML input.
Ideally you are responsible to write templates that should cover all input data. You can do this with 1 or unlimited number of templates. Each template may nest another. This relates to inherited hierarchy of XML.
Furthermore you should be aware that there is priority and precedence applied on templates. It determines order of execution and resolve conflicts if two templates match same data.
Sample:
<xsl:template match="persons">
<!-- Render any data related to all persons -->
<!-- Here nesting happens. XSLT processor will search for templates in rest of XSLT document that match XML data from this contextual point/node -->
<xsl:apply-templates/>
</xsl:template>
Following template matches person and renders it inside above <xsl:apply-templates/>
<xsl:template match="person">
<xsl:value-of select="first-name"/>
<xsl:value-of select="last-name"/>
</xsl:template>
Built-in templates
By default XSLT processor will catch and render all data from source XML that hasn't been processed by your templates. Of course this is rarely wanted behavior.
Dimitre Novatchev has written templates that override these built-in template and outputs descriptive warning about missing matches for elements, nodes, attributes which is very helpful.
<!-- Built-in templates: Explicit -->
<xsl:template match="*" mode="#all" priority="-999">
<xsl:message>
Unmatched element <xsl:value-of select="name()"/>
</xsl:message>
<xsl:apply-templates mode="#current"/>
</xsl:template>
<xsl:template match="text()" mode="#all">
<xsl:message>Unmatched text node</xsl:message>
"<xsl:value-of select="string(.)"/>"
</xsl:template>
<xsl:template match="@*" mode="#all">
<xsl:message>
Unmatched attribute <xsl:value-of select="name()"/>
</xsl:message>
<xsl:value-of select="string(.)"/>
</xsl:template>
Overriding templates
If you explicitly don't want to render some data just write empty template:
<xsl:template match="person" />
Pull vs Push stlye
This:
<xsl:apply-templates />
; is push style. We didn't target which explicit templates we want here so they'l get pushed in document order.
When following template gets executed:
<xsl:template match="name|age|profession">
<td><xsl:value-of select="."/></td>
</xsl:template>
; we can't force order in which name, age or profession are rendered. Order is determined by input XML data. To change this use pull style.
For XSLT 1.0 use:
<xsl:apply-templates select="name"/>
<xsl:apply-templates select="age"/>
<xsl:apply-templates select="profession"/>
This way we explicitly match place to render with code that renders it with select attribute.
Variables
They follow naming and expression that you should know from XPath.
<xsl:variable name="personsCount" select="count(person)"/>
<xsl:value-of select="$personsCount"/>
When defined as child of top <xsl:stylesheet> element it is global.
Here is an example of local:
<xsl:variable name="fullName" select="concat(name,' ',age)"/>
<xsl:value-of select="$fullName"/>
Modularity
As in procedural languages you can place your XSLT code in separate files or modules.
You reference these modules using :
- <xsl:include>
- <xsl:import>
Code included with Include has higher importance. It is treated as if it was written in primary stylesheet. If by mistake you INCLUDE same code you'll create conflict. Include instruction may be placed anywhere.
Import on the other hand can't create conflict in primar stylesheet. It's content is always treated with less precedence and priority than one in primary stylesheet. You must write it as the very first child of <xsl:stylesheet>
Precedence is determined by order of IMPORT instructions. Last one wins.
Precedence
When 2 or more templates match same XML content XSLT processor must choose a winner.
This is usually case for complex xslt comprised from multiple import/includes.
In such cases same match in different xslt modules may occur.
One solution is to play with priority attribute of template instruction:
<xsl:template match="name|age|profession">
<td><xsl:value-of select="."/></td>
</xsl:template>
<xsl:template match="name|age|profession">
<td style="color:red">
<xsl:value-of select="."/>
</td>
</xsl:template>
Observe in above sample that both templates match same data. There will be no error and LAST template in document order will be the winner.
Alternatively we could change first template like this:
<xsl:template match="name|age|profession" priority="2">
This way the first template would win.
Same rule goes for variables. Variable from imported module has LESS priority then same one in primary stylesheet.
Data types
<xsl:variable name="salary" select="xs:decimal(0.1)"/>
For-each
Loop is very similar to apply templates.
There is support for sorting:
<xsl:for-each select="person">
<xsl:sort data-type ="text" select="age" order="descending"/>
<p>
<xsl:value-of select="name"/>
<xsl:value-of select="age"/>
<xsl:value-of select="profession"/>
</p>
</xsl:for-each>
Sorting
You can perform sorting on both for-each and apply-templates instructions on same way:
<xsl:apply-templates>
<xsl:sort data-type ="text" select="age" order="descending"/>
</xsl:apply-templates>
Apply-templates vs for-each
Dimitre Novatchev made great example for this:
XML document:
<creatures>
<animal species="dog"/>
<animal species="cat"/>
</creatures>
XSLT document:
<xsl:template match="creatures">
<xsl:apply-templates mode="say"/>
</xsl:template>
<xsl:template match="animal[@species='dog']" mode="say">
Dog says: "Bow" ...
</xsl:template>
<xsl:template match="animal[@species='cat']" mode="say">
Cat says: "Meauu" ...
</xsl:template>
<xsl:template match="text()" mode="say"/>
Foreach is functionally equivalent foreach in C#. Apply template can be viewed as virtual method.
In above example first template resembles abstract class. It creates generic behavior for functionality Say of animals. Than more specialized templates handle specific cases for each animal. We could say it resembles overriding virtual methods.
Observe last template. If all fails it gets executed. Do note use of mode attribute.
Bottom line is to use for-each for simple tasks and apply-templates for complex problems that are easier solved using more than one place for code.
XSLT 2.0 and 1.0 Foundations by Dimitre Novatchev
You can't learn XSLT without XPath.
XSLT is built around concept of templates.
XSLT can use one or even more XML as input data. Templates can be viewed as peace of code that must target using XPath some elements of XML input.
Ideally you are responsible to write templates that should cover all input data. You can do this with 1 or unlimited number of templates. Each template may nest another. This relates to inherited hierarchy of XML.
Furthermore you should be aware that there is priority and precedence applied on templates. It determines order of execution and resolve conflicts if two templates match same data.
Sample:
<xsl:template match="persons">
<!-- Render any data related to all persons -->
<!-- Here nesting happens. XSLT processor will search for templates in rest of XSLT document that match XML data from this contextual point/node -->
<xsl:apply-templates/>
</xsl:template>
Following template matches person and renders it inside above <xsl:apply-templates/>
<xsl:template match="person">
<xsl:value-of select="first-name"/>
<xsl:value-of select="last-name"/>
</xsl:template>
Built-in templates
By default XSLT processor will catch and render all data from source XML that hasn't been processed by your templates. Of course this is rarely wanted behavior.
Dimitre Novatchev has written templates that override these built-in template and outputs descriptive warning about missing matches for elements, nodes, attributes which is very helpful.
<!-- Built-in templates: Explicit -->
<xsl:template match="*" mode="#all" priority="-999">
<xsl:message>
Unmatched element <xsl:value-of select="name()"/>
</xsl:message>
<xsl:apply-templates mode="#current"/>
</xsl:template>
<xsl:template match="text()" mode="#all">
<xsl:message>Unmatched text node</xsl:message>
"<xsl:value-of select="string(.)"/>"
</xsl:template>
<xsl:template match="@*" mode="#all">
<xsl:message>
Unmatched attribute <xsl:value-of select="name()"/>
</xsl:message>
<xsl:value-of select="string(.)"/>
</xsl:template>
Overriding templates
If you explicitly don't want to render some data just write empty template:
<xsl:template match="person" />
Pull vs Push stlye
This:
<xsl:apply-templates />
; is push style. We didn't target which explicit templates we want here so they'l get pushed in document order.
When following template gets executed:
<xsl:template match="name|age|profession">
<td><xsl:value-of select="."/></td>
</xsl:template>
; we can't force order in which name, age or profession are rendered. Order is determined by input XML data. To change this use pull style.
For XSLT 1.0 use:
<xsl:apply-templates select="name"/>
<xsl:apply-templates select="age"/>
<xsl:apply-templates select="profession"/>
This way we explicitly match place to render with code that renders it with select attribute.
Variables
They follow naming and expression that you should know from XPath.
<xsl:variable name="personsCount" select="count(person)"/>
<xsl:value-of select="$personsCount"/>
When defined as child of top <xsl:stylesheet> element it is global.
Here is an example of local:
<xsl:variable name="fullName" select="concat(name,' ',age)"/>
<xsl:value-of select="$fullName"/>
Modularity
As in procedural languages you can place your XSLT code in separate files or modules.
You reference these modules using :
- <xsl:include>
- <xsl:import>
Code included with Include has higher importance. It is treated as if it was written in primary stylesheet. If by mistake you INCLUDE same code you'll create conflict. Include instruction may be placed anywhere.
Import on the other hand can't create conflict in primar stylesheet. It's content is always treated with less precedence and priority than one in primary stylesheet. You must write it as the very first child of <xsl:stylesheet>
Precedence is determined by order of IMPORT instructions. Last one wins.
Precedence
When 2 or more templates match same XML content XSLT processor must choose a winner.
This is usually case for complex xslt comprised from multiple import/includes.
In such cases same match in different xslt modules may occur.
One solution is to play with priority attribute of template instruction:
<xsl:template match="name|age|profession">
<td><xsl:value-of select="."/></td>
</xsl:template>
<xsl:template match="name|age|profession">
<td style="color:red">
<xsl:value-of select="."/>
</td>
</xsl:template>
Observe in above sample that both templates match same data. There will be no error and LAST template in document order will be the winner.
Alternatively we could change first template like this:
<xsl:template match="name|age|profession" priority="2">
This way the first template would win.
Same rule goes for variables. Variable from imported module has LESS priority then same one in primary stylesheet.
Data types
<xsl:variable name="salary" select="xs:decimal(0.1)"/>
For-each
Loop is very similar to apply templates.
There is support for sorting:
<xsl:for-each select="person">
<xsl:sort data-type ="text" select="age" order="descending"/>
<p>
<xsl:value-of select="name"/>
<xsl:value-of select="age"/>
<xsl:value-of select="profession"/>
</p>
</xsl:for-each>
Sorting
You can perform sorting on both for-each and apply-templates instructions on same way:
<xsl:apply-templates>
<xsl:sort data-type ="text" select="age" order="descending"/>
</xsl:apply-templates>
Apply-templates vs for-each
Dimitre Novatchev made great example for this:
XML document:
<creatures>
<animal species="dog"/>
<animal species="cat"/>
</creatures>
XSLT document:
<xsl:template match="creatures">
<xsl:apply-templates mode="say"/>
</xsl:template>
<xsl:template match="animal[@species='dog']" mode="say">
Dog says: "Bow" ...
</xsl:template>
<xsl:template match="animal[@species='cat']" mode="say">
Cat says: "Meauu" ...
</xsl:template>
<xsl:template match="text()" mode="say"/>
Foreach is functionally equivalent foreach in C#. Apply template can be viewed as virtual method.
In above example first template resembles abstract class. It creates generic behavior for functionality Say of animals. Than more specialized templates handle specific cases for each animal. We could say it resembles overriding virtual methods.
Observe last template. If all fails it gets executed. Do note use of mode attribute.
Bottom line is to use for-each for simple tasks and apply-templates for complex problems that are easier solved using more than one place for code.
Aug 29, 2017
XPath - Examples
// equals descendant-or-self::node()/
Watch it! // is expensive since it is relative path and has to traverse all tree!
Case sensitive names of nodes, elements and attributes !
//Person is not equal //person
Everything inside [ ] is expression. When you need another expression inside [ ] sometimes you can write:
//person[address/city]
; in this case / is used inside [] instead of :
//person[address[city]]
Relative and absolute path
Example of relative path:
//person[1]
; this will return EVERY person that is the FIRST child of its parent ! In sample this will include "Oliver child person" and John Sullivan.
Another relative:
//*/*/*/*/name()
; every element that has 4 ancestors ( city -> address -> person -> persons -> root
String='city'
String='person'
String='city'
Absolute path:
/persons/person[1]
; or use :
(//person)[1]
; this will return only FIRST child of persons node!
Sample XML:
<?xml-stylesheet type="text/xml" href="persons.xsl"?>
<persons>
<person>
<id>1</id>
<age>20</age>
<first-name>
John
</first-name>
<last-name>
Sullivan
</last-name>
<salary>200.00</salary>
</person>
<person>
<id>2</id>
<age>25</age>
<first-name>
Mark
</first-name>
<last-name>
Johny
</last-name>
</person>
<person>
<address>
<city state="France">Paris</city>
</address>
<id>3</id>
<age>30</age>
<first-name>
Mark
</first-name>
<last-name>
Johny
</last-name>
</person>
<person>
<address>
<person>
Oliver child person
</person>
<city state="UK">London</city>
</address>
<id>4</id>
<age>40</age>
<first-name>
Oliver
</first-name>
<last-name>
Johny
</last-name>
<salary>300.00</salary>
</person>
<person>
<id>5</id>
<age>60</age>
<first-name>
Kris
</first-name>
<last-name>
Sullivan
</last-name>
<salary>300.00</salary>
</person>
</persons>
1. Get all persons:
//person
2. Get all persons text:
//person/string()
3. Get second person:
//person[2]
;returns: Mark, Johny, Id=2
4. Get fourth person:
//person[position() eq 4]
;returns: Oliver, Johny, Id=4
5. Get first two persons:
//person[position() lt 3]
6. Get persons that have element Salary:
//person[salary]
7. Get every person whose next person sibling in document order has salary that equals to preceding person.
//person[sallary = following-sibling::person/sallary]
8. Get persons whose age is between 20 and 60 and has position before filtering greater than 3 :
//person[age gt "20" and age lt "60" and position() gt 3]
9. Find persons whose salary is greater than salary of first person that has info about salary:
//person[salary gt //person[salary][1]/salary/text() ]
10. Look for persons that have City info. For them look their parent Person and person Id.
//person/address/city/../../id
11. Find cities whose attribute State is France:
//person/address/city[@state="France"]
Example of sequences introduced in XPath 2.0:
12. Iterate through all persons and output first-name value:
for $n in /persons/person return $n/first-name
13. Iterate all persons with value for salary. On each iteration calculate second sequence by multiplying current person id element value from from first sequence with 2.
for $n in /persons/person[salary], $id in $n/id * 2 return $id
14. Are there any person that has salary greater than $299.00 :
every $p in /persons/person/salary satisfies $p gt "299.00"
;returns true
15. Do all persons older than 18 have salary element ?
every $adult in /persons/person[age gt "30"] satisfies $adult[salary]
;returns true
16. Do at least one person that have city info have salary info:
some $personwcity in /persons/person/address/city satisfies $personwcity/../..[salary]
;returns true
17. Show last Person from Persons node:
/persons/person[last()]
18. Show first-name of persons whose Id is greater than 3. Observe use of dot as self reference.
/persons/person/id[. gt "3"]/../first-name
19. Show first and last person.
(//person)[1] union (//person)[last()]
20. Show only persons with city info and salary info
Version 1:
//person[address/city] intersect //person[salary]
Version 2:
//person[address/city and salary]
21. Show persons that DON'T have salary:
//person except //person[salary]
22. Show all persons ONLY if there are 2 or more persons with address info:
//person[count(/persons/person/address) ge 2]
Watch it! // is expensive since it is relative path and has to traverse all tree!
Case sensitive names of nodes, elements and attributes !
//Person is not equal //person
Everything inside [ ] is expression. When you need another expression inside [ ] sometimes you can write:
//person[address/city]
; in this case / is used inside [] instead of :
//person[address[city]]
Relative and absolute path
Example of relative path:
//person[1]
; this will return EVERY person that is the FIRST child of its parent ! In sample this will include "Oliver child person" and John Sullivan.
Another relative:
//*/*/*/*/name()
; every element that has 4 ancestors ( city -> address -> person -> persons -> root
String='city'
String='person'
String='city'
Absolute path:
/persons/person[1]
; or use :
(//person)[1]
; this will return only FIRST child of persons node!
Sample XML:
<?xml-stylesheet type="text/xml" href="persons.xsl"?>
<persons>
<person>
<id>1</id>
<age>20</age>
<first-name>
John
</first-name>
<last-name>
Sullivan
</last-name>
<salary>200.00</salary>
</person>
<person>
<id>2</id>
<age>25</age>
<first-name>
Mark
</first-name>
<last-name>
Johny
</last-name>
</person>
<person>
<address>
<city state="France">Paris</city>
</address>
<id>3</id>
<age>30</age>
<first-name>
Mark
</first-name>
<last-name>
Johny
</last-name>
</person>
<person>
<address>
<person>
Oliver child person
</person>
<city state="UK">London</city>
</address>
<id>4</id>
<age>40</age>
<first-name>
Oliver
</first-name>
<last-name>
Johny
</last-name>
<salary>300.00</salary>
</person>
<person>
<id>5</id>
<age>60</age>
<first-name>
Kris
</first-name>
<last-name>
Sullivan
</last-name>
<salary>300.00</salary>
</person>
</persons>
1. Get all persons:
//person
2. Get all persons text:
//person/string()
3. Get second person:
//person[2]
;returns: Mark, Johny, Id=2
4. Get fourth person:
//person[position() eq 4]
;returns: Oliver, Johny, Id=4
5. Get first two persons:
//person[position() lt 3]
6. Get persons that have element Salary:
//person[salary]
7. Get every person whose next person sibling in document order has salary that equals to preceding person.
//person[sallary = following-sibling::person/sallary]
8. Get persons whose age is between 20 and 60 and has position before filtering greater than 3 :
//person[age gt "20" and age lt "60" and position() gt 3]
9. Find persons whose salary is greater than salary of first person that has info about salary:
//person[salary gt //person[salary][1]/salary/text() ]
10. Look for persons that have City info. For them look their parent Person and person Id.
//person/address/city/../../id
11. Find cities whose attribute State is France:
//person/address/city[@state="France"]
Example of sequences introduced in XPath 2.0:
12. Iterate through all persons and output first-name value:
for $n in /persons/person return $n/first-name
13. Iterate all persons with value for salary. On each iteration calculate second sequence by multiplying current person id element value from from first sequence with 2.
for $n in /persons/person[salary], $id in $n/id * 2 return $id
14. Are there any person that has salary greater than $299.00 :
every $p in /persons/person/salary satisfies $p gt "299.00"
;returns true
15. Do all persons older than 18 have salary element ?
every $adult in /persons/person[age gt "30"] satisfies $adult[salary]
;returns true
16. Do at least one person that have city info have salary info:
some $personwcity in /persons/person/address/city satisfies $personwcity/../..[salary]
;returns true
17. Show last Person from Persons node:
/persons/person[last()]
18. Show first-name of persons whose Id is greater than 3. Observe use of dot as self reference.
/persons/person/id[. gt "3"]/../first-name
19. Show first and last person.
(//person)[1] union (//person)[last()]
20. Show only persons with city info and salary info
Version 1:
//person[address/city] intersect //person[salary]
Version 2:
//person[address/city and salary]
21. Show persons that DON'T have salary:
//person except //person[salary]
22. Show all persons ONLY if there are 2 or more persons with address info:
//person[count(/persons/person/address) ge 2]
Aug 21, 2017
T-SQL - sample data script - creating random data
If you want more data just add to cross joins more sys tables.
Be careful since row count grows exponentially.
CREATE TABLE Department (
DepartmentID int primary key not null identity,
[Name] nvarchar(4000)
)
CREATE TABLE Employee (
EmployeeID int primary key not null identity,
DepartmentID int,
constraint fk_employee_department foreign key (departmentid) references department(departmentid),
[Name] nvarchar(4000)
)
--Creating roughly 100000 dummy rows
INSERT INTO Department (Name)
SELECT
sys.objects.[Name]
FROM
sys.objects, sys.indexes, sys.tables
--Creating roughly 600000 dummy rows
INSERT INTO Employee (
DepartmentID, [Name]
)
SELECT
ASCII(LEFT(newid(),1)) AS DepartmentID,
sys.columns.[Name]
FROM
sys.objects, sys.columns, sys.tables
Aug 18, 2017
jquery / CSS selector - multiple class delimited with space, comma and greater then
When selecting more then one css class in jQuery or CSS stylesheet one must understand the subtle differences. When to use space, comma and greater then.
Let's take a look at this HTML:
<div id="level1" class="parent">
<span id="spanL1">L1</span>
<div id="level2">
<span id="spanL2">L2</span>
<div id="level3" class="child">
<span id="spanL3">L3</span>
Dummy
</div>
</div>
</div>
<div id="level11" class="sibling">
<span id="spanL11" class="child">L11</span>
<div id="level22">
<span id="spanL22">L22</span>
<div id="level33">
<span id="spanL33" class="child">L33</span>
Dummy
</div>
</div>
</div>
Here are jQuery selectors and their effect :
//Hides L3
$('.parent .child').hide();
//Hides L3 and L33
$('.child').hide();
//Hides L1, L2, L3 & L11 & L33 - makes no sense since class child is contained by class parent
$('.parent, .child').hide();
// Nothing! Since class child is not direct child of class parent
$('.parent > .child').hide();
//Hides L11 since L11 is first child of sibling and L33 is not
$('.sibling > .child').hide();
Let's take a look at this HTML:
<div id="level1" class="parent">
<span id="spanL1">L1</span>
<div id="level2">
<span id="spanL2">L2</span>
<div id="level3" class="child">
<span id="spanL3">L3</span>
Dummy
</div>
</div>
</div>
<div id="level11" class="sibling">
<span id="spanL11" class="child">L11</span>
<div id="level22">
<span id="spanL22">L22</span>
<div id="level33">
<span id="spanL33" class="child">L33</span>
Dummy
</div>
</div>
</div>
Here are jQuery selectors and their effect :
//Hides L3
$('.parent .child').hide();
//Hides L3 and L33
$('.child').hide();
//Hides L1, L2, L3 & L11 & L33 - makes no sense since class child is contained by class parent
$('.parent, .child').hide();
// Nothing! Since class child is not direct child of class parent
$('.parent > .child').hide();
//Hides L11 since L11 is first child of sibling and L33 is not
$('.sibling > .child').hide();
Bottom line:
- space - Inheritance ( parent child )
- comma - enumerating (column1, column2)
- greater then - direct successor (parent > directChild)
Example for inheritance:
<div class="login2">
<div class="form-group">
<input type="submit" value="@Lsr("Users.Login.Login")" class="btn btn-primary" />
<input type="submit" name="ForgotPassword" class="btn btn-link" />
</div>
</div>
I want to override first CSS selector with second:
.login2 INPUT[type="submit"]:hover {
background-color: #4B86B7
}
// DOES NOT OVERRIDE!
.login2 .btn .btn-link INPUT[type="submit"]:hover {
background-color: white
}
//OK !
.login2 .form-group INPUT[type="submit"]:hover {
background-color: white
}
CSS selector is selected based on more specific selector BUT as you can see winner is parent->child specificity and NOT putting a lot of CSS class on one level together.
Example for inheritance:
<div class="login2">
<div class="form-group">
<input type="submit" value="@Lsr("Users.Login.Login")" class="btn btn-primary" />
<input type="submit" name="ForgotPassword" class="btn btn-link" />
</div>
</div>
I want to override first CSS selector with second:
.login2 INPUT[type="submit"]:hover {
background-color: #4B86B7
}
// DOES NOT OVERRIDE!
.login2 .btn .btn-link INPUT[type="submit"]:hover {
background-color: white
}
//OK !
.login2 .form-group INPUT[type="submit"]:hover {
background-color: white
}
CSS selector is selected based on more specific selector BUT as you can see winner is parent->child specificity and NOT putting a lot of CSS class on one level together.
JQuery find() vs children() vs filter()
For HTML:
$('#level1').on('click',function(event){
console.log("level1 click");
$(this).children('span').hide();
});
: this code:<div id="level1"><span id="spanL1">L1</span><div id="level2"><span id="spanL2">L2</span><div id="level3"><span id="spanL3">L3</span>Dummy</div></div></div>
$('#level1').on('click',function(event){
console.log("level1 click");
$(this).children('span').hide();
});
; will hide only L1 since it is first child of Level1 div.
If instead we use:
$(this).find('span').hide();
; all spans will be hidden.
Filter on the other hand is applied only to already found set of elements.
For example:
$(this).filter('span').hide();
; can't work since filter is applied on single DIV element.
This will work:
$(this).find('span').filter(':first').hide();
Alternative and probably more used is using filter as item iterator :
$(this).find('span').filter(function(index){
console.log($(this).text());
});
});
Javascript - JQuery - DOM event propagation
For HTML:
<div id="level1">
<div id="level2">
<div id="level3">
Dummy
</div>
</div>
</div>
; and event handlers for all div's:
$('#level1').on('click',function(event){
console.log("level1");
});
$('#level2').on('click',function(event){
console.log("level2");
});
$('#level3').on('click',function(event){
console.log("level3");
});
; event click will be first handled in innermost level3 and then bubbled up to its parents.
level3
level2
level1
To prevent event bubbling we use event.stopPropagation();
When placed in level3 other levels wont get executed:
level3
Modern browsers support alternative propagation model - capturing. When writing event handler it must be explicitly specified. Capturing works opposite from bubbling. It first handles outermost elements and then executes all children handlers.
For years I've believed that: event.preventDefault() is preventing event bubbling.
For this href:
<a href="www.google.com">Google</a>
; and event handler:
$('a').on('click',function(event){
event.preventDefault();
console.log("google.com");
})
; it prevents standard browser action for HREF so no redirect happens.
<div id="level1">
<div id="level2">
<div id="level3">
Dummy
</div>
</div>
</div>
; and event handlers for all div's:
$('#level1').on('click',function(event){
console.log("level1");
});
$('#level2').on('click',function(event){
console.log("level2");
});
$('#level3').on('click',function(event){
console.log("level3");
});
; event click will be first handled in innermost level3 and then bubbled up to its parents.
level3
level2
level1
To prevent event bubbling we use event.stopPropagation();
When placed in level3 other levels wont get executed:
level3
Modern browsers support alternative propagation model - capturing. When writing event handler it must be explicitly specified. Capturing works opposite from bubbling. It first handles outermost elements and then executes all children handlers.
For years I've believed that: event.preventDefault() is preventing event bubbling.
For this href:
<a href="www.google.com">Google</a>
; and event handler:
$('a').on('click',function(event){
event.preventDefault();
console.log("google.com");
})
; it prevents standard browser action for HREF so no redirect happens.
Subscribe to:
Posts (Atom)