# Feature requests > **Know a fix that should be included in SOUP (or an issue that could be fixed)? List it here.** ### Scheduled for next release These fixes have been added to the [v1.3 development branch](https://github.com/vyznev/soup/blob/devel/SOUP.user.js), and will be included in SOUP v1.4: * [The branch prediction answer is overflowing](http://meta.stackoverflow.com/q/214706) * [Confirming context menu entries via Enter triggers comment to be posted](http://meta.stackoverflow.com/q/66646) and [Pressing <Enter> in an input method editor should not submit comments](http://meta.stackoverflow.com/q/216834) (these are actually the same fix) * [Turn off MathJax noErrors extension during preview](http://meta.math.stackexchange.com/q/12512) (see suggestion by Davide Cervone below) * [MathJax preview broken when equations contain `\label`s](http://meta.math.stackexchange.com/q/11392) * Also, the fix for [Can we have the suggested questions' titles parsed by default?](http://meta.math.stackexchange.com/q/11036) will also be applied to the question and answer panels on the user profile summary page. ### Possible additions These issues might be fixed in a future release, but need some work first: * [Make Stack Exchange sites compatible to OS X Lion full screen mode](http://meta.stackoverflow.com/q/113212): This should be easy enough to fix, but I'd need to find a Mac to reproduce it on first. * [Feature request: user script or option to turn off instant MathJax rendering](http://meta.math.stackexchange.com/q/2558) (MathJax): Might be worth it, even though it means adding an extra UI element. * [Any chance of MathJax in chat?](http://meta.stackoverflow.com/q/97938) (MathJax, chat): Probably too major a change for SOUP, plus limited utility unless enabled for _all_ users. See http://stackapps.com/questions/4370/google-chrome-chat-mathjax-extension and [ChatJax](http://meta.math.stackexchange.com/questions/1088/should-chat-have-tex-support/3297#3297) for alternative implementations. ### Declined: These issues are out of scope for SOUP, or cannot be easily fixed: * [LaTeX in post preview is slow](http://meta.cs.stackexchange.com/questions/222/latex-in-post-preview-is-slow) (MathJax): Probably too difficult to fix reliably; could reconsider if it turns out not to be. See [A prototype for incremental preview updates](http://meta.math.stackexchange.com/questions/4208/a-prototype-for-incremental-preview-updates) for an existing user script that attempts this, and [Feature request: user script or option to turn off instant MathJax rendering](http://meta.math.stackexchange.com/q/2558) for an alternative workaround. * [Viewing single answers in math-heavy threads takes too long](http://meta.cs.stackexchange.com/q/538) (MathJax): The fix itself is actually quite easy (just set the `elements` option in MathJax config), but it does no good — typesetting the rest of the page causes the text to jump up and down so much that you still have to wait for it to finish before you can actually read anything. Seems effectively unfixable. :-( ### Proposed: Feel free to add new proposals here. I propose adding a MathJax hook that does two things: 1. Reset the equation numbers and labels, so that when editing a post that has a labeled equation, you don't fall prey to the multiply defined label problem (where the math is no longer displayed because of the error). 2. Temporarily disable the noErrors extension so that (when editing a post) you will see the actual error messages rather than just the TeX code in a block. (But only when editing a post, not when they are being displayed otherwise.) To do this, I recommend adding the following: > MathJax.Hub.Register.MessageHook("Begin Process",function (message) { if (message[1].id && message[1].id.match(/^wmd-preview/)) { MathJax.InputJax.TeX.resetEquationNumbers(); MathJax.Hub.Config({TeX:{noErrors:{disabled:true}}}); } }); MathJax.Hub.Register.MessageHook("End Process",function (message) { if (message[1].id && message[1].id.match(/^wmd-preview/)) { MathJax.Hub.Config({TeX:{noError:{disabled:false}}}); } }); This operates only when the math being typeset is in a Markdown preview window, and the noErrors extension is turned back on when the typesetting is done.