-
Notifications
You must be signed in to change notification settings - Fork 36
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
TinyMCE API key requirement message hides the menu #262
Comments
Bump on this. Quack is great and an extra bump goes to the "move to different open-source HTML Rich editor component." |
Facing the same issue.How to move to different HTML rich editor? Any setting ? |
Bump, we're running into the same issue and the text boxes are completely unusable due to it. If there's no way to put in an API key or switch to a different rich editor component then quack has essentially become useless for us. |
Fixed in cloud |
Describe the bug
After opening TestCases tab with registered Test Cases, a message about TinyMCE API registration appears and hides the app menu.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No warning messages are shown
Screenshots
Expected behavior:
Actual behavior:
Desktop (please complete the following information):
Additional context
It looks like TinyMCE begins to require API key in the next year. At least there should be a way (maybe through config file) to provide this key to the TinyMCE Editor component. But as the developer states on their official site https://www.tiny.cloud/pricing/ , free plan only includes 1000 loads / month. I don't know what counts for 1 load (there are multiple requests to TinyMCE CDN for each test case, the more steps it contains, the more requests are issued. Is each one considered as 1 load?), but it may be too restricted for some scenarios.
So, maybe you should consider using the different CDN to avoid API Key requirements (such as https://cdnjs.com/libraries/tinymce ), or move to different open-source HTML Rich editor component.
The text was updated successfully, but these errors were encountered: