4 ms·

Thanks for the info. It looks like you chose to embed Chromium for rendering markdown? What was the reason for not using an embedded IE instance (which is alrea

Thanks for the info. It looks like you chose to embed Chromium for rendering markdown? What was the reason for not using an embedded IE instance (which is already part of every Windows installation).

protolif 14y ago
Probably because IE is a giant failboat.
xpaulbettsx 14y ago
IE doesn't participate in the WPF rendering system, so it would have all kinds of glitches like it sitting above all other controls (referred to in the docs as "Airspace Issues"), as well as unthemed controls (specifically the scroll bar - stuck out like a sore thumb). The markup that READMEs use is really simple, IE would've been fine for it.
- erode 14y ago
  Airspace issues have been the bane of my existence until WPF3.5sp1. D3DImage! Side note -- I also advocate Caliburn.Micro, it's great!
deleted 14y ago
[deleted]