If you use the mdpopups dependency for tooltips, and wish it had the same functionality for phantoms, now it does.
Additionally, 2 new template variable were added: is_phantom and is_popup. These can be used to create custom CSS that differs for phantoms and popups.
Read more in the docs: http://facelessuser.github.io/sublime-markdown-popups/usage/
Unfortunately itās not possible to use the PhantomSet API from ST with this because you didnāt add a subclass of Phantom with its constructor (and __eq__) changed. I donāt have any use for this currently, but just mentioning~
The PhantomSet class only adds and deletes Phantoms on the view that have changed when you call its .update method.
Okay 1.61 is released with Phantom and PhantomSet classes. Good catch. Thanks @FichteFoll! That makes dealing with phantoms better.
My versioned repo was in a separate place from the installed Sublime installed version. They were not quite in sync and the template lib had not been updated which broke everything.
1.6.2 is out and fixes all thatā¦(man I really need to throw in some tests to catch stuff like this)
1.7.0 is released
Noticeable change is going to be that font sizes are now based off of the font size in the current view they are created in. Other than that, there are a couple of new API methods for getting style of a specific scope in the color scheme, tinting an image with a color, and raw variants of image API commands that return the raw byte string opposed to a base64 encoded img element (useful if you want to save an image in a cache or something).
Made some adjustments to relative font sizes as it seems assuming the font size in the settings file as a px gives a more reliable feel. That should be found in 1.7.1.
I am working on support for scaling with high dpi monitors. I have something working on Windows, but I will provide a manual setting for OSX and Linux as I am not sure how to detect font scaling on those systems. I am hoping after the next release I will stop fiddling with this for a while.
High Dpi workaround is in 1.7.2 . If you need to manually scale it for OSX and Linux, you can. You can also override the Windows guessing with your own scale, but hopefully that is not needed.
See the following for more info:
Thatās it for now.
New version out. Main things are that we now use the better CSS support that was introduced in 3119+. I added things like options to wrap your content in a div with a class so you can have CSS like .myplugin .myclass {} etc. It still supports the legacy CSS for now, but that will be removed when the next ST beta drops.
Also supports templating in your HTML/Markdown content. You can send in template variables or configure your content template environment by changing the template tags or adding filters etc. Variables are available in both CSS and content under the plugin object, but the template environment options only apply to your HTML/Markdown content. I donāt need people mucking with the CSS environment 
.
For those who donāt like the idea of me tweaking the default popup/phantom css, Iāve added a sublime setting to turn off the base formatting. You will loose things like definition lists etc. Put you will have a pure ST formatting then. The default color styling CSS has been stripped down significantly to allow to let Sublime 3119+ generate CSS or let the themes specify the colors. But it can be overriden by creating a mdpopups.css in your user folder.
Thatās the main stuff, you can see the release notes here https://github.com/facelessuser/sublime-markdown-popups/releases/tag/1.9.0.
Most of my plugins that use mdpopups will be updated to better use this stuff moving forward.
As always, let me know of any bugs.
Hello, I use the BracketHighlighter package that now require mdpopups 1.9.0, I run Package Controlās Satisfy Dependency command, but the version is still 1.8.0, how can I install the new version? Thanks.
I had the same problem this morning - I think Package Controlās dependency logic is flawed - my solution was just to go Packages -> Browse Packages, delete the mdpopups folder and restart ST, to force it to download the latest version.
@wbond Iāve got the same problems as stated above by @TheShrike and @kingkeith.
Iām on Win10 Pro x64 with ST3120 x64 portable. PC is v3.1.2.
I just freaked people out on old ST versions that were too old to even use hover events. I released a new BH to calm people down with a message explaining things. Also, I bumped mdpopups to 1.9.1. Had a bug in implementation. Anyways Iām going to bed .
Mine upgraded to 1.9.1 from 1.9.0 successfully after using Satisfy Dependencies 
(Win 7 x64, ST3120)
Thanks. I would be a typo Iāve copied and pasted between 3 repos though 
.
New version out 1.11.0.
The only change is that block code tags will no longer wrap. Inline code should still wrap.
New version out:
Released Nov 27, 2016
NEW: Mdpopups now handles CSS color names in color schemes.
Didnāt realize CSS color name support was added in color schemes. Be aware if you start putting CSS color names in your color scheme files, you may break plugins that are unaware that Sublime Text can do this. I didnāt even know this was possible until yesterday. Mdpopups will now support it, but I know I have other plugins that havenāt been updated to support this yet.
Iām sure when people are aware of this, there are going to be lots of color schemes that start using CSS color names. I am hoping I will have all my plugins updated by then to avoid people filing issues.
ā Chang Log