-
Notifications
You must be signed in to change notification settings - Fork 8.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
Remove ace #30139
Comments
Adding the |
Maybe https://github.com/codemirror/codemirror ? Looks pretty lightweight (~160kb): https://bundlephobia.com/[email protected] Not sure whether all necessary features are provided though. |
Codemirror is definitely good choice for these. And you should consider supporting its author as well. |
@epixa I know it's been awhile, but I figured it was worth asking -- do we have any information regarding Ace editor's accessibility and security deficiencies? I also checked out the Ace changelog and it seems fairly actively maintained. Do you have any information to the contrary? |
@cjcenizal Sorry, I don't really remember the context here. I should have provided it in the issue. Based on the timing, at least from a security standpoint I suspect the issue was around our efforts to roll out Content Security Policy. Either Ace didn't support |
Resurrecting the CSP discussion, I discovered that
As I noted in #140388, it looks possible to run edit: it appears that cc @elastic/kibana-security |
The
ace
project at best is not aligned with our priorities in terms of accessibility and security, and at worst it is effectively abandoned entirely. Either way, it's not suitable for use in Kibana and we should remove it entirely.First, we must decide which editor to switch to. The monaco editor is an option, but it's very large (>=5mb) and not mobile-friendly at all, so it's probably not the best option in most places in Kibana. We don't necessarily need only a single editor if we want to differentiate between robust editor capabilities and more lightly editing.
Suggestions of an alternative are welcome, even if on a plugin by plugin basis.
We should address this throughout 7.x and have it closed out in 8.0. These are the plugins that use brace or ace today:
The text was updated successfully, but these errors were encountered: