Strangely the comma bug seems to have been fixed, but in doing so they re-introduced the old buggy behaviour where when you’re asked to retype an answer containing commas that you got wrong, it stops accepting further input the moment you type a comma. For courses with lots of sentences it’s extremely annoying and the “comma bug” at least gave some temporary relief from it…
Parentheses and hyphens are still being marked “literally” though.
I’ve only been here for 2-3 months and this is how the phrases with commas have behaved during all this time. You can only retype until the first comma.
I’m aware of that but it’s clearly incorrect. In fact it’s worse than how I described, it’s not when you type a comma, it’s when you type up to the part of the answer that has a comma that it stops accepting input.
I still have the problem. “close” would be correct and enough to get a correct answer, now i have to introduce “close, near”, this is just one example from many, many words…
broken.
it’s not just stops accepting but you are suddenly on the next page typing the rest of your previous answer in the new form which results in a new mistake 
I totally agree with you but with all the mess on the site now, not sure if it is worth even complaining.
On the learning review screen after you got something wrong, where it “auto-enters” as soon as you’ve completed a correct answer (even if it’s a subset of a longer correct answer), it always stopped you at the first comma like that. I’ve been using memrise since 2012, and that was always just how it worked. Annoying, but I think a better fix for it would be to eliminate the auto-enter aspect of that screen.
I’ve actually worked out how to fix that, there’s function “set_for_complete” that gets called when you’ve typed a complete answer, that if you remove the last 3 statements from will prevent it from automatically moving to the next item (but you do see a “tick” telling you that the answer is considered complete). Will look at a way it can be done using a Tampermonkey type script.
Actually I reckon we could fix quite a few of the existing Memrise bugs with this sort of thing (e.g. the parenthesis bug), though not anything that’s clearly a back-end problem.
Ok, got it, you need a script that executes every time you open www.memrise.com (e.g. using TamperMonkey) that does this:
MEMRISE.garden.box_types.CopyTypingBox.prototype.set_for_complete = function() {this.correct=!0,this.$marking_icon.addClass(“tick”),this.$input.addClass(“correct bounce”).removeClass(“incorrect”) }
Like I said, this will still show the “tick” automatically when it considers you have a complete answer, but also allow to keep typing to enter the “full” answer, and you’ll have to hit “ENTER” to move to the next question.
BTW: as a non-web-developer, with absolutely zero familiarity with the code, and using only a minified version of the source (with no comments or helpful variable/function names), I was able to fix this in 30 minutes. If I had access to the full source I’d need maybe 10 minutes. That’s why I’m absolutely stunned it took them 4 or 5 days (or even weeks in the case of the ‘comma’ bug) to fix some the recent issues.
Seems to be working pretty well with TamperMonkey, for that you’ll need:
// ==UserScript==
// @name Fix auto-complete on copy-typing
// @match http://www.memrise.com/*
// ==/UserScript==
if (MEMRISE.garden) MEMRISE.garden.box_types.CopyTypingBox.prototype.set_for_complete = function() {this.correct=!0,this.$marking_icon.addClass(“tick”),this.$input.addClass(“correct bounce”).removeClass(“incorrect”); }