Selector for one tag directly followed by another tag
You can’t in css.
Edit: To be a bit more helpful, if you use for example jQuery (a JavaScript library), you can use .prev()
.
Select first occurring element after another element
#many .more.selectors h4 + p { ... }
This is called the adjacent sibling selector.
Select an element that comes before another element with the same class in CSS
If I understand it correctly, you want
.alert {
margin-bottom: 0;
}
.alert:last-child {
margin-bottom: 20px;
}
@import 'https://maxcdn.bootstrapcdn.com/bootstrap/3.3.5/css/bootstrap.min.css';
.alert {
margin-bottom: 0;
}
.alert:last-child {
margin-bottom: 20px;
}
<div class="alert alert-success" role="alert">The <code>margin-bottom: 20px</code> was overriden by <code>margin-bottom: 0</code>.</div>
<div class="alert alert-info" role="alert">The <code>margin-bottom: 20px</code> was overriden by <code>margin-bottom: 0</code>.</div>
<div class="alert alert-warning" role="alert">The <code>margin-bottom: 20px</code> was overriden by <code>margin-bottom: 20px</code>.</div>
Select element not followed by another
Is this what you mean? Then you're almost there.
DEMO
/* will select p not directly followed by div.red */
#myContainer > p + div:not(.red)
How to use CSS to select an element only if a specific element comes after the one you want to select?
It's not possible in CSS3, the best you can do is select only the <ul>
which follow <p>
:
p + ul { /*...*/ }
However it will be possible when browsers start implementing the CSS4 subject operator:
!p + ul { /*...*/ }
In the meantime, you'll have to use jQuery and walk the DOM back.
CSS selector - Selecting specific tags inside a parent class
- you should use
>
for that>
will be used when you want a property value to be applied to specific element not for all element.
.new1>h1,
.new1>p {
color: purple;
text-align: center;
}
<p>This is a paragraph.</p>
<section class="new1">
<p> Helloooo </p>
<h1> Hiiii! </h1>
</section>
<section class="new2">
<p> Hello </p>
<h1> Hi! </h1>
</section>
Can I select an element that's not immediately after another, e.g. :not(.foo + .bar)?
It's worth noting that :not(.foo + .bar)
is valid in Selectors 4, and implementations are on their way. Having said that, due to the nature of the adjacent sibling combinator +
(and similarly the child combinator >
), there is a Selectors 3 equivalent, although you will need a list of up to three complex selectors:
:first-child, :not(.foo) + *, .foo + :not(.bar)
But this is a direct conversion that accounts for elements that are not .bar
. More likely, you just want to match any .bar
that's not directly preceded by a .foo
. In that case, it gets even simpler:
.bar:first-child, :not(.foo) + .bar
And you can pick and choose further depending on your needs:
- If not being preceded by a
.foo
means.bar
becomes the first child, you can just use.bar:first-child
. - If
.bar
is guaranteed to have a preceding sibling, you can just use:not(.foo) + .bar
.
If you need to account for both possibilities, then listing both as shown above will do just fine.
Note that the .foo
and .bar
selectors don't necessarily have to be different. You can match any .bar
that's not immediately preceded by another .bar
with the exact same technique.
How do I select an element based on the state of another element in the page with CSS?
The general answer to the canonical question
How do I select an element based on the state of another element in the page with CSS?
is that it depends on exactly three conditions:
- whether the state of these elements can be represented using simple selectors,
- whether a structural relationship can be expressed between these two elements using combinators to form a single complex selector, and
- whether the element that you want to target can be made the subject of the resulting complex selector.
While the current Selectors standard has some interesting and sometimes potentially powerful features, the way it is designed makes it extremely limited in area #2 (with #3 being a direct consequence). Some of these limited possibilities are enumerated in other answers, e.g. through the most basic use of child and sibling combinators, clever use of dynamic pseudo-classes (which actually relates to condition #1), or a combination of both.
The problem given in the question, on the other hand, cannot be solved using what is currently available in Selectors for this reason. Most of this boils down to the lack of either a parent selector and/or a previous sibling selector, both of which may seem like trivial features, but have certain implications that make them difficult to define or implement well. In summary:
Yes, the state of these elements can be represented using simple selectors:
div
and[data-status~=finished]
for the former, and.blink
and.spin
for the latter two.The first element can be represented by
section > div[data-status~=finished]
, and the two subject elements can be represented bysection + section > .blink
andsection + section > .spin
respectively. The problem is that it's not possible to write a complex selector incorporating all of these structures, because combinators are one-way, and there is no parent counterpart to the child combinator to join them at the firstsection
element.Assuming the answer to the first two questions is also "yes", each of
.blink
and.spin
can be made the subject of its own complex selector. (But more on that in the next section.)
If you've been directed to this question, chances are the problem you're trying to solve, like the one given above, cannot be solved with Selectors due to these limitations.
The upcoming standard boasts some new features that will greatly enrich selector syntax and potentially open it (and CSS) up to a host of new possibilities, including a possible solution to the example problem. All of these things will be covered in the following sections, but first I'll explain what each condition means and how it relates to the given example:
Element states, and structural relationships between elements
The defining characteristic of a selector is that it represents a certain structure of one or more elements in the document tree. This isn't just something I made up — you can actually find this description in the informative overview of the Selectors standard:
A Selector represents a structure. This structure can be used as a condition (e.g. in a CSS rule) that determines which elements a selector matches in the document tree, or as a flat description of the HTML or XML fragment corresponding to that structure.
Selectors may range from simple element names to rich contextual representations.
Each element is represented by a sequence of one or more simple selectors. This sequence is known as a compound selector (I'm using terminology from Selectors 4 here as it is much clearer than what is used in Selectors 3 — see this answer for a non-exhaustive list of terms).
Each simple selector represents a certain state of an element. There are simple selectors for matching the type (or tag name) of an element, a class name, an ID, or an arbitrary attribute. There are also pseudo-classes, which represent abstractions and other special states not directly represented within the document tree, such as the order and position of an element in its hierarchy (:nth-child()
, :nth-of-type()
), user interactions (:hover
, :active
, :focus
, :checked
), the visitedness of a hyperlink (:link
, :visited
), and much more.
In the given example, the div
element with a data-status
attribute whose space-delimited value contains finished
can be represented with a type selector and an attribute selector:
div[data-status~=finished]
If you want the selector to apply only when the pointer is over this element, simply throw in a :hover
pseudo-class:
div[data-status~=finished]:hover
Compound selectors are linked via combinators to form complex selectors. These combinators, the >
, +
and ~
symbols that you may be familiar with, express a relationship between the elements represented by each compound selector. With these two tools alone, you're already able to create some very interesting results as shown in the other answers here. I explain these basics in even further depth in this answer.
In the given example, the following structural relationships can be established:
The first
section
element is the parent ofdiv[data-status~=finished]
. This is represented using the child combinator>
:section > div[data-status~=finished]
The second
section
immediately follows the first one as its sibling. This is represented using the adjacent sibling combinator+
:section + section
Additionally, the second
section
is the parent of both.blink
and.spin
. This can be represented using two selectors, one for each child:section + section > .blink,
section + section > .spinWhy are two selectors required? In this case it's mainly because there is currently no syntax for subgrouping two compound selectors into one, so you will have to represent each child element separately. The upcoming Selectors 4 standard introduces a
:matches()
pseudo-class that will provide this very subgrouping functionality:section + section > :matches(.blink, .spin)
Now, since every compound selector in a complex selector represents one element, and thus section + section
represents two elements that are siblings, section > div
represents a parent and a child, and section + section > div
represents a child of a next-sibling, you would think that a parent combinator and a previous-sibling combinator are quite redundant. So why do we commonly get these questions:
- Is there a CSS parent selector?
- Is there a "previous sibling" CSS selector?
And, more importantly, why is the answer to both of these questions no? The reason is addressed in the next point:
Subject of a selector
The subject of a selector is always represented by the rightmost compound selector. For example, the selector section + section > div
represents three elements, of which div
is the subject. You might say that the div
is selected, or targeted, as in the question, but if you've ever wondered if there was a proper term, it's known as the subject of the selector.
In a CSS rule, styles are applied to the element represented by the subject of the selector. Any child boxes and pseudo-element boxes inherit the styles from this element where appropriate. (The exception is if the subject of the selector includes a pseudo-element, in which case the styles are applied directly to the pseudo-element only.)
Taking the selectors from the previous section, we have the following:
- The subject of
section > div[data-status~=finished]
isdiv[data-status~=finished]
. - The subject of
section + section
is the secondsection
selector. - The subjects of
section + section > .blink, section + section > .spin
are.blink
and.spin
respectively. - Using
:matches()
, the subject ofsection + section > :matches(.blink, .spin)
is:matches(.blink, .spin)
.
It might seem therefore that we do need a parent selector or a previous-sibling selector. But remember that selectors can already represent complex structures. Instead of simply adding new combinators that work opposite of existing ones, it makes sense to seek out a more flexible solution, and that is exactly what the CSSWG has been doing.
Which brings us to the following from the original question:
Is there a CSS selector that would let me specify which elements should get selected based on target element state?
The answer to this is no, and will remain no. However, in the earlier drafts of Selectors 4 (from the FPWD up to the latest working draft from May 2013), there was a proposal for a new feature that would let you pick any of the compound selectors other than the rightmost one, and designate that as the subject of the selector.
A potential solution
However, the subject indicator was recently removed in favor of the :has()
pseudo-class (that was in turn adopted from jQuery). I speculate on a likely reason here:
The reason
:has()
is more versatile is because, with the subject selector, it was never made clear in any draft if a single complex selector could have more than one subject selector (since a single complex selector can only ever have one subject) and/or if functional pseudo-classes such as:matches()
accepted the subject selector. But because a pseudo-class is a simple selector, you know that:has()
can be accepted anywhere a pseudo-class is accepted.
So while you cannot change the subject of a selector, :has()
will completely write off the need to do so, due to its pseudo-class nature. And the best part is that it does this — and then some — all without fundamentally changing selector syntax.
In fact, the example problem can be solved using Selectors 4's :has()
:
/* Combined with the :matches() example from above */
section:has(> div[data-status~=finished]) + section > div:matches(.blink, .spin)
Notice the use of a child combinator: this scopes the relative selector argument to just children of the first section
. Yes, this is the elusive "parent selector" that Web developers the world over have been wanting for years.
And since :has()
comes from jQuery, you can use it today, although :matches()
doesn't exist yet so you'll have to replace that with a call to .filter()
in the meantime:
$('section:has(> div[data-status~=finished]) + section > div')
.filter('.blink, .spin')
.css('color', 'red');
<script src="https://ajax.googleapis.com/ajax/libs/jquery/2.1.1/jquery.min.js"></script>
<section>
<div>Element 1</div>
<div data-status="finished">Element 2</div>
<div>Element 3</div>
</section>
<section>
<div>Element 4</div>
<div class="blink">Element 5</div>
<div>Element 4</div>
<div>Element 4</div>
<div class="spin">Element 4</div>
...
</section>
Related Topics
Css3 Radial Gradients with Rgba()
How to Add Background Images in a Jsf Application Using Richfaces and CSS
How to Set CSS Only for Specific Ie Browsers
How to Remove Letter-Spacing for the Last Letter of an Element in CSS
CSS Sticky Header/Footer and Fully Stretched Middle Area
Angular 2 Animation VS CSS Animation - When to Use What
CSS Float, Clear a "Row" of Floating Elements
How to Use CSS Media Query to Scale Background-Image to Viewing Window
Is There a CSS Workaround for Firefox' Bug: Inline-Block + First-Letter with Changed Size
Target IE9 or IE8 But Not Both Using CSS
CSS Transform Scale, Don't Scale Child Element
@Page :First { Margin: ... } in Chrome Bug
Seek to Specific Keyframe in CSS3 Animation
Rendering Font Differs from Ie Compared to Ff and Chrome
How to Animate Multiple CSS Transform Properties Separately Using Keyframe Animation
What Are the Differences Between Display:Box and Display:Flexbox