-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Can't edit (but can see) images from cross domains #207
Comments
The same issue happens to me with this file: although the s3 is configured property with cross-origin enabled to all domains (with also, I executed on terminal: |
After talking to Froala's support team, they also suggested it's related to TAU. |
Hi, @jinwoo-kim-nhn do you have any suggestions for what it could be? |
@seonim-ryu maybe you can help here? |
@junghwan-park any updates? |
@seonim-ryu @junghwan-park hello guys, are you going to do something with it? |
@romanfedyshyn Sorry for the late reply. |
Hi, just want to ask if you do something with that? |
I have same issue. |
This issue has been automatically marked as inactive because there hasn’t been much going on it lately. It is going to be closed after 7 days. Thanks! |
This issue will be closed due to inactivity. Thanks for your contribution! |
Version
3.5.2
Development Environment
MacOS Mojave
Node.js 10.14.0
React 16.8.6
Current Behavior
When using image href of cross domains - I get a "No 'Access-Control-Allow-Origin' header is present on the requested resource" error.
I can see the image (using froala) before opening the TUI advanced-editor, but when opening the advanced editor I get the "No 'Access-Control-Allow-Origin' header is present on the requested resource" error and therefore can't see (inside the advanced-editor) nor edit the image.
Expected Behavior
Being able to see and edit cross-domains images in TUI advanced editor
The text was updated successfully, but these errors were encountered: