Adjust UX in new folder/file creation dialog - #1938
Conversation
|
@LukasHirt I'll need your help to debug the value/input value issue. I tried passing in a default value for the text using either |
7d60057 to
0d072ab
Compare
|
I've added automated tests |
💥 Acceptance tests webUITrashbin failed. Please find the screenshots inside ...https://drone.owncloud.com/owncloud/phoenix/5041/
|
💥 Acceptance tests failed. Please find the screenshots inside ...https://drone.owncloud.com/owncloud/phoenix/5041/
|
💥 Acceptance tests failed. Please find the screenshots inside ...https://drone.owncloud.com/owncloud/phoenix/5041/
|
💥 Acceptance tests webUIRenameFiles failed. Please find the screenshots inside ...https://drone.owncloud.com/owncloud/phoenix/5041/
|
💥 Acceptance tests webUIFiles failed. Please find the screenshots inside ...https://drone.owncloud.com/owncloud/phoenix/5041/
|
💥 Acceptance tests webUIFiles failed. Please find the screenshots inside ...https://drone.owncloud.com/owncloud/phoenix/5042/
|
💥 Acceptance tests webUIRenameFiles failed. Please find the screenshots inside ...https://drone.owncloud.com/owncloud/phoenix/5042/
|
I'll take a look. |
|
@PVince81 The problem with the value is that it's not passed as a prop. If you use only |
@LukasHirt there is already a property called "value". Or do you mean I need to pass it as "value=xxx" without the colon ? |
|
or is the property passing around missing inside the oc dialog prompt maybe ? |
|
With this you'd lose the variable and it would write the string directly without translations
Yes, the value is in the oc-text-input component but is not being assigned in the dialog component. The input then doesn't know about the value. |
|
@LukasHirt but the "oc-text-input" is using "inputValue" as model and I see it being copied around in the code below the template. I tried evaluating both and none is set from outside despite |
|
according to https://github.com/owncloud/phoenix/blob/newfiledialog-adjust-ux/apps/files/src/components/ocDialogPrompt.vue#L73 this would copy However for some reason |
But since |
|
@LukasHirt see my last comment. The value is being copied from |
|
From what I see the rename dialog is receiving a value and it works. I'll check how that one is doing it. Apparently it doesn't use the "value" property directly in the markup. |
5fd395a to
9739443
Compare
|
Default value is now fixed using the same approach as rename dialog. |
💥 Acceptance tests failed. Please find the screenshots inside ...https://drone.owncloud.com/owncloud/phoenix/5047/
|
💥 Acceptance tests failed. Please find the screenshots inside ...https://drone.owncloud.com/owncloud/phoenix/5047/
|
💥 Acceptance tests webUIFiles failed. Please find the screenshots inside ...https://drone.owncloud.com/owncloud/phoenix/5047/
|
It takes |
- empty name now shows an error - added default value - added placeholder text
Use class name instead of id for the oc-dialog alert prompt element, because Selenium would not see the element if there are multiple elements with the same id, even if the others are invisible.
When calling clearValue(), Vue's v-model do not detect any change events so the "empty folder name" validation fails to trigger. This adds a workaround with a new custom command clearValueWithEvent() that will simulate clearing the field with keyboard keys instead of programmatically.
Tests fail randomly when the test runner would click on the "+ new" file menu before it becomes enabled. This extends the selector to wait for an enabled button to appear before clicking.
f6d5115 to
e300128
Compare
|
What an adventure! Just dealt with random failures which are fixed now:
|
|
This is ready for review |
|
I'd also like to know if my additions to the testing code are ok @individual-it |























































































Description
Related Issue
Motivation and Context
See ticket
How Has This Been Tested?
Manual test:
Screenshots (if appropriate):
Types of changes
Checklist:
Open tasks: