UI: Contacts form validation — Create button not disabled when required fields empty #50
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_os#50
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
In the new contact form, the "Create Contact" button is visually styled as disabled (has
hero-btn-disabledclass) butisDisabled()returnsfalse. The button should be properly disabled (not just styled) when required fields (Name, Public Key) are empty.Additionally, clicking the disabled-looking button produces no error message or validation feedback.
Steps to Reproduce
Expected
disabledattribute when required fields are emptySeverity
Low — the button is visually indicated as disabled, just not semantically
Screenshots
deep_contacts_02_new_form.png