I'd love to say we hand colour everything by hand, but we don't. We have scripts that do that.
Our auto-language detection does need work, but the main problem was you had <...> in the code and it wasn't HTML encoded. Our scripts can partially deal with this, but sometimes they think you're adding special HTML and try and close open tags.
I... had... okay, you're right. Absolutely did not see that one while hand-encoding the stuff. I first thought I'd need to write that HTML file and started from the template, but eventually took a look at your submission "wizard" (form) and there was that WYSIWYG editor. Thanks for fixing it then.
That is the XML/HTML autocomplete thing jumping in. You have to use the < and > HTML character entities to prevent that. I still think that the XML/HTML autocomplete system should be turned OFF in code blocks.
Look at this page: Windows Runtime
Are you changing something or is it broken?
It had General and How-to sections. Now it only has Sponsored articles. And it looks like the most of recent related articles disappeared from this page.
Update: it looks like articles from this section can't be edited: look at this message
I can't edit my article either. For this one I got message that I have no permission to edit it.
And for my and for some other articles from this section I don't see revisions history.
Well, looks like it has been fixed today. I still wonder whether you did something about that. It would be nice to have few words in reply to such bugs. Just to be aware of what happend.
I'm wondering whether I should have another go at a d3js article, and if I do it would be nice to make the examples come alive. That would require the ability to add scripts to the page, like: <script src="http://d3js.org/d3.v3.min.js">