Isaac Muse

I believe the latest wxPython supports SVGs, but I think the biggest holdup with this is creating SVGs that don't suck 🙃. So far, all we have is a logo....

@gir-bot remove S: triage @gir-bot add T: feature

Why don't you provide a custom CSS file in your package and have the user include it in there user CSS using `{{'Packages/MyPackage/custom.css'|getcss}}` ([reference](http://facelessuser.github.io/sublime-markdown-popups/styling/#include-css-filter))? Does this seem reasonable? The idea...

I think there are some misunderstandings about how this works. 1. A plugin's CSS does only affect a plugin's popup. 2. MdPopups default CSS does only affects popups from plugins...

I'm also very much of the opinion that the user should have the last word with the user CSS. People's opinion differ on things, just as some of my opinions...

> and besides that even the popup_css setting in the color scheme can still be overridden by a color scheme customization in the User package. Yup, and all of that...

Since the suggested priority can't be changed as requested, I will go ahead and close this issue.

I think what is really being described here is CSS specificity. We don't have `body#mdpopups`, but we have `div.mdpopups`. This provides us with something very similar. So to get this...

The flow of priority will still be the same, so if a plugin uses equal or greater specificity, they will override the scheme, but I think this is a reasonable...

We dump debug info before we wrap. I'm going to have to look into this and experiment. I can't yet comment as I have only theorized this so far.