Form Save UX

Approaches:

• a) Enable when valid
  • Pro: Simple, what many BP forms due today (copy/pasted)
  • Con: Shows enabled when there are not changes
  • Con: Because we only show errors on touched fields, the user might see "Save is disabled" even when there are no red errors on the screen (although they would probably see * for required fields)
• b) Enable whenever dirty, even if valid
  • Pro: Only enables when changes to save
  • Con: Shows enabled even when they are visible & invisible validation errors

Scenarios:

1. A new form (creating author), that is totally empty

• Currently we do not show validation errors until fields are touched, so likely invalid but no errors showing
• If we show "Submit" enabled, clicking Submit "touches" all the fields, and you see the errors

2. An edit form (editing author) with no changes

• Initially dirty=false & valid=true -> Save is disabled

3. A duplicate from (creating new author from existing)

• dirty=false (technically user hasn't changed anything)
• valid=true