Skip to content

Can you bring back form-input, form-select, etc? #20

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jeffsawatzky opened this issue Nov 30, 2020 · 3 comments
Closed

Can you bring back form-input, form-select, etc? #20

jeffsawatzky opened this issue Nov 30, 2020 · 3 comments

Comments

@jeffsawatzky
Copy link

Hello, I use emberjs, along with the ember-power-select addon for custom select boxes. Ember-power-select uses a div for the select trigger and not a select element. Previously I was able to style it with tailwind-custom-forms using a form-select class, but now I can't.

Its great that we don't need to add these classes to normal form elements, but sometimes we need to style a non-form element as one, and these classes made it easy.

@zeppelin
Copy link

When transitioning from an existing CSS framework to Tailwind, it'd be great if elements were not targeted directly - or at least an option existed to specify classnames to avoid clashes. That would solve the above use-case, and also avoid vendor lock-in to this plugin.

@chasegiunta
Copy link
Contributor

Related to #11

@adamwathan
Copy link
Member

Added a new class strategy in v0.3.0 that should handle this, thanks to @chasegiunta 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants