-
Notifications
You must be signed in to change notification settings - Fork 470
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Turn off Image Drag and Drop Into WYSIWYG Field #21466
Comments
this was fixed on this ticket #19956 |
This should be enabled by default and only be disabled if the config |
The D&D to those fields is not working in the release branch |
Internal QA: I think it needs work Now, it is enabled by default which is correct. But when I disable it, the component behaves a bit odd because it doesn't add the image but opens it in a new tab. I've recorded a video with more details: Screen.Recording.2022-05-20.at.5.39.00.PM.mov |
that's the normal behaviour of the browser when a file is dragged into a html page, IMO not an issue |
As this is the expected behavior, I'm passing the internal QA |
Fixed, now this is working as expected. Tested on release-22.06 // Docker // FF |
Is your feature request related to a problem? Please describe.
When users drag and drop local image files into the WYSIWYG editor, they files are uploaded as a binary into the root folder. This makes it difficult for editors to find these images again.
Please see this ticket for additional context: https://dotcms.zendesk.com/agent/tickets/106063
Describe the solution you'd like
Create the ability to prohibit drag and drop of images into the WYSIWYG editor
Describe alternatives you've considered
When an image is dropped into the WYSIWYG editor, allow for a menu to pop up that enables a selection of where the binary will be stored in the folder structure.
Additional context
As per this request: #19972 if turning off the ability to upload via drag and drop is not an option, then perhaps the alternative solution of selecting where the binary can be stored can be similar to the suggested solution for the above request
The text was updated successfully, but these errors were encountered: