Multiple dropzones on a page

Question

Multiple dropzones on a page

Igor-Golovtsov opened this issue 3 years ago · 9 comments

Hello.
When using two or more drop zone components on the same page, a bug occurs. When you click on the first component, the file selection window opens, after selecting the file, the file selection window of the second component immediately opens. When closing the second window, both components break without an error, they just don't work. A unique ID or ref does not correct the situation.
Do you have any suggestions on how to fix this?

Thank you and I apologize for my English.

Answer 1 · 2021-09-07T14:52:06.000Z

I'll check on the weekend ^^

Answer 2 · 2021-09-10T15:52:56.000Z

in the DropZone.Vue component we should create a parameter for the ref or maybe we should create a random ref for each instance.
What should be better in your opinion?

Answer 3 · 2021-09-14T10:39:42.000Z

It seems to me that the best choice is an optional parameter.

Answer 4 · 2021-09-14T11:26:41.000Z

When i use dropzoneRef, i have error

Uncaught (in promise) TypeError: Cannot read property 'classList' of undefined
    at eval (dropzone-vue.common.js?cd1f:6)
    at Array.forEach (<anonymous>)
    at initHiddenFileInput (dropzone-vue.common.js?cd1f:6)
    at eval (dropzone-vue.common.js?cd1f:6)
    at callWithErrorHandling (runtime-core.esm-bundler.js?5c40:6990)
    at callWithAsyncErrorHandling (runtime-core.esm-bundler.js?5c40:6999)
    at Array.hook.__weh.hook.__weh (runtime-core.esm-bundler.js?5c40:2270)
    at flushPostFlushCbs (runtime-core.esm-bundler.js?5c40:7191)
    at flushJobs (runtime-core.esm-bundler.js?5c40:7228)

but, without dropzoneRef everything is fine

Answer 5 · 2021-09-16T21:16:24.000Z

It's right the component should use the new ref in order to find some internal element. I'll try to fix it soon as possible

Answer 6 · 2021-09-18T11:13:47.000Z

use the different class names for each instance. you can use the dropzoneClassName prop for change. It helps me.

Answer 7 · 2021-10-29T06:27:21.000Z

Is the issue resolved? I'm facing the same issue. Tried using different class names but didn't helped.

Thanks

Answer 8 · 2021-11-25T06:02:03.000Z

This appears to be happening because the clickable event is registered on .dropzone__message, and when there are multiple elements with the same class, it's re-registering it on the first one.

I've pushed up a PR which instead uses the class/value passed in dropzoneMessageClassName to register the event. You will need to pass in a custom message class name, i.e. dropzone-message-class-name="dropzone__message--my_custom_class", which is unique for each instance. There might be a better way to do it, but this satisfies my use case.

In the meantime, feel free to use npm i @jaseeey/dropzone-vue until the issue is addressed. I've just done this now, hopefully no issues :)

Answer 9 · 2021-12-02T17:11:01.000Z

fixed version 0.1.11