You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a larger CSS files which contains a few base64-encoded fonts. (the css file is ~800kb of which 650kb are the fonts). I noticed a considerable slowdown, similar to what has previously been described in #143.
I tested removing all base64 fonts, and Emmet is blazingly fast. For context, I used a fresh install of the plugin, without any changes to the configuration in Emmet.sublime-settings (setting auto_mark to false also didn't result in any noticeable speedup).
Not sure about how exactly Emmet works, but considering the format, would it maybe be possible for emmet to simply ignore things base64-encoded lines? (or all of @font-face, if that's easier to implement?)
I have a larger CSS files which contains a few base64-encoded fonts. (the css file is ~800kb of which 650kb are the fonts). I noticed a considerable slowdown, similar to what has previously been described in #143.
I tested removing all base64 fonts, and Emmet is blazingly fast. For context, I used a fresh install of the plugin, without any changes to the configuration in
Emmet.sublime-settings
(settingauto_mark
to false also didn't result in any noticeable speedup).Not sure about how exactly Emmet works, but considering the format, would it maybe be possible for emmet to simply ignore things base64-encoded lines? (or all of
@font-face
, if that's easier to implement?)The text was updated successfully, but these errors were encountered: