-
-
Notifications
You must be signed in to change notification settings - Fork 147
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
Klipse 7.7.1 exposes globals to window #330
Comments
This is annoying. |
You can try oldest Klipse version following the instructions here |
Yesterday morning I happened to hold a presentation where I used a Klipse powered playground. This morning I noticed that the playground no longer worked (IOW, that |
OK. I will look at it further. Do yo want to use a previous version until I am fixing the bug? |
Thanks! There is no hurry. I might try pinning the Klipse version this evening. |
One temporary workaround would be to use the non-minified version of Klipse. |
Check. FYI, I have now pinned the Klipse version to |
Hmm... It seems that Klipse 7.7.1 writes its globals with minimized names to the window object. This breaks all of my Klipse based pages as they expose a few JavaScript libraries with short names like
R
andL
to the window for the snippets to use. With 7.7.1 those names are overwritten by Klipse and the snippets no longer work. For example, the Fastener library page is broken. If you open the browser console runObject.keys(window)
and inspect the result you can see the exposed globals.The text was updated successfully, but these errors were encountered: