-
Notifications
You must be signed in to change notification settings - Fork 8
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
Allow destroying (detaching) the inspector #42
Milestone
Comments
You don't want to detach it from an editor instance but to kill the application entirely? Am I getting this right? |
Yes, I want to kill it completely, so it stops affecting the JS execution results. |
ma2ciek
added a commit
that referenced
this issue
Sep 20, 2019
Feature: Allowed attaching the inspector collapsed using a configuration passed to `CKEditorInspector#attach()`. Implemented the `CKEditorInspector#destroy()` method. Unified `CKEditorInspector#attach()` arguments syntax and allowed attaching to multiple instances at a time. Closes #44. Closes #42. Closes #48. BREAKING CHANGE: The `CKEditorInspector.attach( 'editor-name', editor );` syntax was deprecated and replaced by an object literal `CKEditorInspector.attach( { 'editor-name': editor, ... } );`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was trying to check one thing in our manual tests but I realised that the inspector is affecting the results. It'd be good if it was possible (even via console) to kill it.
The text was updated successfully, but these errors were encountered: