#153 - button behaviour in form editing #164
Reference in New Issue
Block a user
No description provided.
Delete Branch "#153-behaviour-of-buttons"
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?
This should close #153
Changed for:
Presentation:
https://user-images.githubusercontent.com/1353655/172369461-f1bdd0db-21e7-4c09-8c0c-739e8cf637f0.mp4
disabled:opacity-60
will be better than this gray color, because it suggest to user that the button is clickable but it doesn't. It applies to all submit buttons in editing forms.Maybe we can add this button behaviour on other forms - I mean form for creating resources.
I'm not sure, if hover is okay, when a button is disabled.
@@ -301,2 +300,4 @@
:class="[form.processing || !form.isDirty ? 'disabled:opacity-60' : 'hover:bg-blumilk-700']"
:disabled="form.processing || !form.isDirty"
>
Zapisz
Only on this page the button is not disabled, because of default state. For a while we have null in vacation type, and after that we set first vacation type (depends on user) and in this moment fronted thinks that something change, but it isn't. So, in the line (I mean after
vacationTypes.value = res.data
) 459 writeform.defaults('vacationType',vacationTypes.value[0])
.@@ -301,2 +300,4 @@
:class="[form.processing || !form.isDirty ? 'disabled:opacity-60' : 'hover:bg-blumilk-700']"
:disabled="form.processing || !form.isDirty"
>
Zapisz
Now it should work properly.