The use of __proto__

[Noah Kantrowitz]

So as we have been expanding browser testing, we noticed that the Jade compiler doesn't work on IE right now due to the use of __proto__ for extending classes. Would you (I guess this is mostly aimed at TJ, but happy for feedback from others) be interested in a patch that switches to using .prototype=Object.create(x) style subclassing? This should work the same in Node and other environments which support Object.create (http://kangax.github.io/es5-compat-table/#Object.create, and a polyfill is available for older browsers as well). This would make life easy for us, but I could also see this as being rejected since the only benefit is to a platform I would guess visionmedia has minimal interest in supporting. This is just in an attempt to get our dev environment running on IE to debug IE-specific bugs, in our normal production build using compiled template and jade/runtime, everything works swimmingly in IE.

--Noah

[Matthias]

Hi! Just ran into the same problem, even with IE10. If you hate IE or not, I would like to vote for this request to avoid a buildstep for some projects. 

@noah Please let me know if I can help somehow.

[vision media [ Tj Holowaychuk ]]

we used to compile __proto__ out when producing jade.js but I believe the new maintainer has switched to browserify so that may no longer be the case

--
You received this message because you are subscribed to the Google Groups "Jade" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jadejs+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.