Skip to content
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

css_container is missing from context in widgets with custom templates e.g. CheckboxMultipleSelect #117

Open
grundleborg opened this issue Mar 8, 2022 · 0 comments

Comments

@grundleborg
Copy link
Contributor

I'm not sure if there's a bug here, or if I just don't fully understand what CSSContainer is / how it is supposed to work. When rendering a widget such as CheckboxMultipleSelect which has it's own custom template which does not use the tailwind_field template tag to render the field, the CSS classes are taken from the css_container object. However, this does not appear to be present in the context, so setting the default classes in CrispyTailwindFieldNode.default_styles of tailwind_field.py has no effect. I'm not sure whether I'm expecting the wrong thing to happen here, or whether these widgets with custom templates are not even expected to work yet. Any pointers would be most welcome, as I am trying to get this and a few other widgets working properly for a project, as well as sending PRs to this repo with any fixes and/or missing functionality to arise from this.

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

1 participant