CSS Selector for selecting an element that comes BEFORE another element?
It would be possible to use the 'adjacent sibling selector' if the input
was before the label
. Just put the input
before the label
, and then modify the layout to put label
before the input
. Here's an example:
<head runat="server">
<title></title>
<style type="text/css">
input:focus + label {font-weight: bold}
</style>
</head>
<body>
<form id="form1" runat="server">
<div style="direction:rtl">
<input type="text" id="username" />
<label for="username">Username:</label>
</div>
<div style="direction:rtl">
<input type="password" id="password" />
<label for="password">Password:</label>
</div>
</form>
</body>
(It's kind of a hack, I would personally use javascript to do this)
input:focus + label {font-weight: bold}
<form id="form1" runat="server"> <div style="direction:rtl"> <input type="text" id="username" /> <label for="username">Username:</label> </div> <div style="direction:rtl"> <input type="password" id="password" /> <label for="password">Password:</label> </div></form>
Select specific element before other element
As far as I know, CSS doesn't offer any selectors which will target before a selector. Could you select it as an h2
which is directly after a p
(p + h2
)?
h2 {
color: #1a1a1a;
}
p + h2 {
color: #0cc;
}
Example on JSFiddle
As you can see, this is probably the best selector you can use if you're relying on CSS, although you could easily just add a class to each h2
that is before a ul
. That would avoid the case where you have a paragraph section before another h2
and paragraph section.
You could do this using jQuery:
.highlight {
color: #0cc;
}
$('ul').prev('h2').addClass('highlight')
Example on JSFiddle
This selects every ul
, then selects the h2
that is before it, before finally adding the .highlight
class to it.
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>
Is there a previous sibling selector?
No, there is no "previous sibling" selector.
On a related note, ~
is for general successor sibling (meaning the element comes after this one, but not necessarily immediately after) and is a CSS3 selector. +
is for next sibling and is CSS2.1.
See Adjacent sibling combinator from Selectors Level 3 and 5.7 Adjacent sibling selectors from Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification.
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>
CSS selecting the element located BEFORE another element
This is not possible. Your best option would be to use jQuery. That would give you many options to complete this task.
According to the link below it does look like CSS4 will have the ability to specifiy which element you would like.
Is there a CSS parent selector?
How to select an element appearing after another in css?
Adjacent Sibling Selector (+)
The adjacent sibling selector is used to select an element that is directly after another specific element.
Sibling elements must have the same parent element, and "adjacent" means "immediately following".
The following example selects the first
element that are placed immediately after elements:
H1 + p {
background-color: yellow;
}
Try it here.https://www.w3schools.com/css/css_combinators.asp
Related Topics
Is It Possible Based on CSS to Create a Circle with Gradient Border and Transparent Inner
Ml-Auto Is Not Pushing Navbar Links to the Right
How to Apply Custom Animation Effect @Keyframes in Mui
Have a Fixed Position Div That Needs to Scroll If Content Overflows
How to Give One CSS Class Priority Over Another
Ie Crossing Out Pseudo Element CSS
Does 'Position: Absolute' Conflict with Flexbox
How to Set the Height of a Div Based on a Percentage-Based Width
Align Button at the Bottom of Div Using CSS
How to Style the Ul List to a Single Line
How to Match 3D Perspective of Real Photo and Object in CSS3 3D Transforms
Rounded Side, Not Rounded Corners
Overflow to Left Instead of Right
Perspective and Translatez Moves Diagonally
How to Disable the Clear Button That Ie10 Inserts into Textboxes