Tailwindcss: Input (::placeholder) utilities

Created on 7 Nov 2017  路  2Comments  路  Source: tailwindlabs/tailwindcss

Last days I've been working with Tailwind and I have just so much fun 馃榾

I was looking for some input utilities but couldn't find them. Maybe I've looked over them, I don't know. I was specific looking for pseudo elements/classes like ::placerholder, ::invalid and so on.

I think it would be great to include them, maybe it is already included in the plans for new releases, or maybe not at all. Thanks anyway!

Most helpful comment

Hey there @glenngijsberts! We don't have any placeholder or invalid utilities right now. They are similar to hover, active and focus, which don't exist (except for some hover states).

The reason is that adding these states for each utility in Tailwind would cause the outputted CSS file size to grow substantially. Ideally it would be great to have these states available on all utilities, but practically it's not smart.

That said, we're are already working on a system where you can enable or disable the responsive, active, focus and hover states on a per module basis.

This is similar to issue #121.

All 2 comments

Hey there @glenngijsberts! We don't have any placeholder or invalid utilities right now. They are similar to hover, active and focus, which don't exist (except for some hover states).

The reason is that adding these states for each utility in Tailwind would cause the outputted CSS file size to grow substantially. Ideally it would be great to have these states available on all utilities, but practically it's not smart.

That said, we're are already working on a system where you can enable or disable the responsive, active, focus and hover states on a per module basis.

This is similar to issue #121.

Consolidate into #136.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ouun picture ouun  路  3Comments

dbpolito picture dbpolito  路  3Comments

afuno picture afuno  路  3Comments

smbdelse picture smbdelse  路  3Comments

benface picture benface  路  3Comments