#36317: ModelChoiceField cannot be hidden by default
-------------------------------+--------------------------------------
Reporter: Josh Piasecki | Owner: (none)
Type: Bug | Status: closed
Component: Forms | Version: 5.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Natalia Bidart):
* resolution: => invalid
* status: new => closed
Comment:
Hello Josh Piasecki, thank you for your ticket!
I believe that the behavior you describe derives from the structure of the
rendered HTML and how CSS `display: none;` affects different elements.
While it may seem like a bug, it aligns with standard HTML and CSS
behavior. Given this, and given that the Django ticket tracker is best
suited for confirmed or reproducible issues within Django itself, I'm
afraid I have to close this as `invalid`.
This particular scenario appears to be more of a usage question or a
request for implementation advice. Therefore, it would be more appropriate
to discuss this on the [https://forum.djangoproject.com/c/users/forms-
formsets/18 Django Forum], where community members can provide guidance
and potential solutions. If, through community discussion, this is
identified as a potential improvement for Django, we can revisit and
consider reopening the ticket. Thank you for your understanding.
--
Ticket URL: <https://code.djangoproject.com/ticket/36317#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019621438f54-2c2973e9-95ab-407a-9d21-bc2d995611c0-000000%40eu-central-1.amazonses.com.