Robin Ward

@davidtaylorhq I'm not sure how we approve things for chat providers we don't use ourselves.

Discourse does still use it, but we are committed to upgrading to commonmark, so we will unfortunately be migrating to markdown-it this year :(

That error seemed about 1.4.5, this one is 1.5.2; locally I can run the default grunt task and everything works (with nicer output!). Maybe give it a shot locally and...

What errors are you getting in grunt? Grunt works totally fine for me with this version. On Thu, Feb 20, 2014 at 2:33 PM, James Herdman [email protected]: > npm test...

That's so strange. I just confirmed again that both `npm test` and `grunt all` work correctly. It must be some kind of platform issue. I'm on node v0.10.24

Bump here -- is there a good reason not to merge this? It is behind an option so it should not affect anyone who doesn't want it.

Looks like a random npm failure to me? I didn't change any deps.

We only use it in browsers so I have no insight into node versions. But 0.8 is quite old isn't it?

I posted this in the issue but `TextureRect` was only used for the minimum reproducible project. In the actual game the texture is rendered on a 3D object (a computer...

Yes I am aware of the SubViewportContainer, I just wanted to keep the MRP simple to illustrate the issue. In my actual game the interface is not a `TextureRect` it's...