id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
27068	Acquire form's initial data more consistently	Jon Dufresne	nobody	"In `BoundField`, sometimes initial data [https://github.com/django/django/blob/698be78d7438aade49d3cac5ea1f9de219d33e42/django/forms/boundfield.py#L222 handles callables]. While other times, [https://github.com/django/django/blob/698be78d7438aade49d3cac5ea1f9de219d33e42/django/forms/boundfield.py#L136 it doesn't]. This can lead to a theoretical bug when the initial data is a callable, but the field is disabled.

Other times, the initial callable is handled, but microseconds are [https://github.com/django/django/blob/698be78d7438aade49d3cac5ea1f9de219d33e42/django/forms/forms.py#L435 not chopped] leading to theoretical false positives that data has changed.

Initial data should be handled more consistently across all cases. 

Marking as a bug due to the theoretical edge cases that can produce unexpected results. Noticed these inconsistencies while working on #27037."	Bug	closed	Forms	dev	Normal	fixed			Ready for checkin	1	0	0	0	0	0