Currently, codemirror diagnostics are styled with a generated svg underline, and I was wondering if there was a reason to do this, rather than using the browser’s native CSS styling.
I ask since a Zettlr (markdown texteditor using CM6) user has reported they experienced noticeable performance improvements by removing the svg-generated underlines. I’d be interested in implementing this app-wide, but I was curious about the rationale before doing so.
If I am not mistaken, Safari has only gotten support for wavy underlines last year, and CodeMirror aims to also work on browsers older than that. Hence the use of SVG by default. But of course you’re welcome to override that if you target only evergreen browsers.
This is good to hear! Zettlr is electron based, so very evergreen 
I’m looking at when the spelling underlines were supported, and its surprisingly recent for all browsers, like within <2 years for all of them. Regardless, thank you for the quick response! I think using the native css will offer a nice performance boost for the app