


Why Don\'t Input Elements Support ::before and ::after Pseudo-Elements?
Unraveling the Puzzle: Why Input Elements Lack ::before and ::after Pseudo-Elements
In an endeavor to enhance default styling for HTML5 input elements, a common issue arises where ::after pseudo-elements fail to render content. Despite numerous attempts and testing across various browsers, the desired visual enhancements remain elusive.
This peculiar behavior has sparked curiosity: why do browsers unanimously dismiss ::after pseudo-elements on input elements? A thorough examination of the CSS specification reveals a crucial detail. According to the CSS21 specification, ::after only applies to elements that possess document tree content. Input elements, along with elements like images and line breaks, do not contain such content, rendering the use of ::after ineffective.
Therefore, the answer lies in the nature of input elements. Unlike elements such as paragraphs or spans that carry textual content, input elements primarily facilitate user interaction and lack content for display purposes. This inherent characteristic prevents the utilization of ::before and ::after pseudo-elements on input elements.
The above is the detailed content of Why Don\'t Input Elements Support ::before and ::after Pseudo-Elements?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

It's out! Congrats to the Vue team for getting it done, I know it was a massive effort and a long time coming. All new docs, as well.

I had someone write in with this very legit question. Lea just blogged about how you can get valid CSS properties themselves from the browser. That's like this.

I'd say "website" fits better than "mobile app" but I like this framing from Max Lynch:

The other day, I spotted this particularly lovely bit from Corey Ginnivan’s website where a collection of cards stack on top of one another as you scroll.

If we need to show documentation to the user directly in the WordPress editor, what is the best way to do it?

There are a number of these desktop apps where the goal is showing your site at different dimensions all at the same time. So you can, for example, be writing

CSS Grid is a collection of properties designed to make layout easier than it’s ever been. Like anything, there's a bit of a learning curve, but Grid is

I see Google Fonts rolled out a new design (Tweet). Compared to the last big redesign, this feels much more iterative. I can barely tell the difference
