css input not empty

Пустому элементу (тот, который не имеет вложенных потомков, в том числе пробелов и переносов строки Enter ), можно задать стиль с помощью псевдокласса :empty [w3.org]. Элементу, содержащему лишь пробельные символы, — псевдокласса :blank [w3.org, пока не поддерживается браузерами].

Как работает :empty

Для input и textarea не так важно заполнены они или нет. Более важно заполнены ли они правильно или нет, а для этого есть псевдоклассы :valid и :invalid

Please complete the security check to access codepen.io

Why do I have to complete a CAPTCHA?

Completing the CAPTCHA proves you are a human and gives you temporary access to the web property.

What can I do to prevent this in the future?

If you are on a personal connection, like at home, you can run an anti-virus scan on your device to make sure it is not infected with malware.

If you are at an office or shared network, you can ask the network administrator to run a scan across the network looking for misconfigured or infected devices.

Another way to prevent getting this page in the future is to use Privacy Pass. You may need to download version 2.0 now from the Chrome Web Store.

Cloudflare Ray ID: 538010ea2ad6c2f9 • Your IP : 78.85.5.224 • Performance & security by Cloudflare

Is it possible to know if an input is empty with only CSS?

I had that question when I tried to make an autocomplete component for Learn JavaScript. Basically, I wanted to:

  1. Hide a dropdown if the input is empty
  2. Show the dropdown if the input is filled

I found a way to do it. It’s not perfect. There are a few nuances involved, but I want to share it with you.

The form

First, let’s build a form so we’re on the same page. We’re going to use a simple form with one input.

When the input is filled, we want to change its border-color to green. Here’s an example of what we’re creating:

Checking if the input is empty

I relied on HTML form validation to check whether the input is empty. That meant I needed a required attribute.

At this point, it works fine when the input is filled. Borders turned green.

But there’s a problem: If the user enters a whitespace into the field, the borders turn green too.

Technically, this is correct. The input is filled because the user typed something into it.

But I didn’t want whitespaces to trigger a blank dropdown menu (for the autocomplete component).

It wasn’t enough. I needed a more stringent check.

Further checks

HTML gives you the ability to validate inputs with regular expressions with the pattern attribute. I decided to test it out.

Since I didn’t want whitespaces to be recognized, I started with the S+ pattern. This pattern meant: One or more characters that’s not a whitespace.

Sure enough, it worked. If a user enters a whitespace into the field, the input doesn’t get validated.

But when a whitespace is entered (anywhere) into the input, the input gets invalidated.

Unfortunately, this pattern didn’t work in my use case.

In Learn JavaScript’s autocomplete component, I taught students how to complete a list of countries. The names of some countries had spaces…

I had to include whitespaces in the mix.

The next best alternative I could think of is S+.* . This means 1 or more non-whitespace characters, followed by zero or more (any) characters.

This worked! I can enter whitespaces into the mix now!

But there’s one more problem… the input doesn’t validate if you START with a whitespace…

And that’s the problem I couldn’t resolve. More on this later.

When I worked on this article, I came across another interesting question: Is it possible to style an invalid state when the input is filled incorrectly?

Invalidating the input

We don’t want to use :invalid because we’ll kickstart the input with an invalid state. (When the input is empty, it’s already invalid).

This is where Chris Coyier swooped in to the rescue with » Form Validation UX in HTML and CSS».

In the article, Chris talks about a :placeholder-shown pseudo-class. It can be used to check whether a placeholder is shown.

  1. You add a placeholder to your input
  2. If the input is hidden, it means the user typed something into the field
  3. Proceed with validation (or invalidation)

Here’s the CSS (simplified version. For the complete version, check out Chris’s article)

Since I had both validation AND invalidation styles, I had to ensure the valid styles came after the invalid styles.

Here’s a demo for you to play with:

Note: Edge doesn’t support :placeholder-shown , so it’s probably not a good idea to use it in production yet. There’s no good way to detect this feature.

Now back to the problem I couldn’t resolve.

The problem with pattern

The pattern attribute is wonderful because it lets you accept a regular expression. This regular expression lets you validate the input with anything you can think of.

But… the regular expression must match the text completely. If the text doesn’t get matched completely, the input gets invalidated.

This created the problem I mentioned above. (Reminder of the problem: If a user enters a whitespace first, the input becomes invalid).

I couldn’t find a regular expression that worked for all use-cases that I thought of. If you want to try your hand at creating a regular expression that I need, I’d be more than welcome to receive the help!

Here are the use-cases:

(Then again, I might be overthinking it… ��).

Update: Problem solved!

Many readers were generous enough to email me their solutions. I want to thank everyone who helped. Thank you so much!

The cleanest solution I received is: .*S.* by Daniel O’Connor. This means:

  • .* : Any character
  • S : Followed one non-whitespace character
  • .* : Followed by any character

Other regexes I received include:

And many others!

Here’s a codepen with the updated solution by Daniel:

Wrapping up

Yes, it is possible to validate a form with pure CSS, but there are potential problems with validation when whitespace characters are involved.

If you don’t mind the whitespaces, it works perfectly. Have fun trying this pattern out! (Sorry, I can’t help it).

Thanks for reading. Did this article help you out? If it did, I hope you consider sharing it. You might help someone else out. Thanks so much!

Comments are closed

Please contact me if you want to talk to me about this article.

If you spot a typo, I’d appreciate if you can correct this page on Github. Thank you!

Оцените статью