You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When selection is in the place where upload is not allowed then d&d upload does not work for the entire document.
Let's assume that image is not allowed in blockquote and upload command is disabled when selection is in blockquote element. Toolbar upload icon should be disabled then, but it should be possible to drop and upload image out of the blockquote.
The text was updated successfully, but these errors were encountered:
The problem is the browser which, in many cases, do not bring the proper position.
This is why I am not sure if image upload should use image upload command. It should work the same way paste works: at this point do not use any command (in the future posibly use clipboard command). This way image paste will be handled the same way paste is handled, might be executed in places where the image command is disabled and moved later to the betters place like in the case of paste (use insertContent?). It will be disabled when clipboard will be disabled.
In make sense, especially when you think about pasting an image from HTML. The same rule should be applied when you paste <p><img></p> (or even a single <img>) and when you paste the image as a file.
Unfortunately, I think we do our best to use target position, see insertAt in:
The problem is the browser which, in many cases, do not bring the proper position.
We can try to work around this by setting model selection to insertAt position before executing the command.
When selection is in the place where upload is not allowed then d&d upload does not work for the entire document.
Let's assume that image is not allowed in blockquote and upload command is disabled when selection is in blockquote element. Toolbar upload icon should be disabled then, but it should be possible to drop and upload image out of the blockquote.
The text was updated successfully, but these errors were encountered: