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
Browser: Chrome OS: Windows/Mac Is React App: True
I applied jodit editor into react + material ui setup into modal window and see that inputs inside image properties are not focusable and not clickable. Everything except this works correctly.
My setup was the following:
Dialog>
//jodit editor placed here
<textarea id="editor" name="editor" />
/Dialog>
The same issue i see with Link popup ( all fields there are not clickable ). I noticed that on version 3.4.x it works correctly, but Image properties has similar issue.
Is this known defect, did someone faced similar behavior before?
Thank you
The text was updated successfully, but these errors were encountered:
Thank you for your answer, after some research i found out that this is mui Dialog functionality prevent focus from leaving the modal while open ( link editor and image editor are separate modals ) and there is a property to disable this behavior:
( screenshot was taken from https://mui.com/material-ui/api/modal/#props ).
To summarize i would like to say that this is not an issue with Jodit editor, but probably it will be a good idea to update documentation of image-editor and link-editor plugins and other plugins which are opening in new modals to warn users about such potential behavior
Jodit Version: 3.18.4
Browser: Chrome
OS: Windows/Mac
Is React App: True
I applied jodit editor into react + material ui setup into modal window and see that inputs inside image properties are not focusable and not clickable. Everything except this works correctly.
My setup was the following:
Dialog>
//jodit editor placed here
<textarea id="editor" name="editor" />
/Dialog>
The same issue i see with Link popup ( all fields there are not clickable ). I noticed that on version 3.4.x it works correctly, but Image properties has similar issue.
Is this known defect, did someone faced similar behavior before?
Thank you
The text was updated successfully, but these errors were encountered: