You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dialog.formDialog looks very similar to widget.Form but, as the code is different, there's a difference: widget.Form considers FormItem.HintText and creates helperOutput text widgets for items, and then it uses the helperOutputs to show validation errors if they occur. dialog.NewForm uses its own code and thus it misses HintText and helperOutput, and thus validation error messages are missed.
To Reproduce:
Steps to reproduce the behaviour:
Run fyne_demo.
Go to Widgets/Form tab.
Enter aaaa to the Email field and click to another field.
The text Your full name will be replaced with not a valid email.
Go to Dialogs tab and click the Form Dialog button.
Try to reproduce the behavior there.
Device (please complete the following information):
OS: Windows
Version: 10
Go version: 1.17.2, 1.18beta2
Fyne version: 2.1.2
The text was updated successfully, but these errors were encountered:
I'm not sure this is quite accurate. The output for validation should be present if there is HintText or Validation set.
However it is indeed possible that the Form dialog gets this wrong, will need further consideration.
Describe the bug:
dialog.formDialog
looks very similar towidget.Form
but, as the code is different, there's a difference:widget.Form
considersFormItem.HintText
and createshelperOutput
text widgets for items, and then it uses thehelperOutput
s to show validation errors if they occur.dialog.NewForm
uses its own code and thus it missesHintText
andhelperOutput
, and thus validation error messages are missed.To Reproduce:
Steps to reproduce the behaviour:
fyne_demo
.Widgets/Form
tab.aaaa
to the Email field and click to another field.Your full name
will be replaced withnot a valid email
.Dialogs
tab and click theForm Dialog
button.Device (please complete the following information):
The text was updated successfully, but these errors were encountered: