Thanks for the advice! The last item is the most important I think, and the reason we didn't originally do this is because the plugin has been cross-platform since launch in 2013. I believe at that time the CSS technique only worked on certain browsers. We have been talking about updating the coloring technique to use CSS, but it hasn't been a top priority compared to everything else we've been doing (both on the browser plugin and on the rest of the business).

I'm going to talk with the team about your suggestion regarding \<pre> blocks. We're early in the process of addressing this issue, which has come up recently. Hope it's a quick fix!