We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider the following example:
selector: [ '.movie[data-id="1"]', '.item-list a[href^="/reservation"]' ]
We want to ensure .movie[data-id="1"] selector matches 1 element, then we want to select the descending .item-list a[href^="/reservation"] element.
.movie[data-id="1"]
.item-list a[href^="/reservation"]
This is different from .movie[data-id="1"] .item-list a[href^="/reservation"]. The latter would match:
.movie[data-id="1"] .item-list a[href^="/reservation"]
<div data-id="1"></div> <div data-id="1"> <div class="list-item"> <a href="/reservation"></a> </div> </div>
The former would not.
An alternative is to allow use of the quantifier expression anywhere in the selector, e.g.
.movie[data-id="1"] {1}[0] .item-list a[href^="/reservation"]
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Consider the following example:
We want to ensure
.movie[data-id="1"]
selector matches 1 element, then we want to select the descending.item-list a[href^="/reservation"]
element.This is different from
.movie[data-id="1"] .item-list a[href^="/reservation"]
. The latter would match:The former would not.
An alternative is to allow use of the quantifier expression anywhere in the selector, e.g.
The text was updated successfully, but these errors were encountered: