prior to this change, if you entered an empty field, turned on bold,
typed some text, and then backspaced over the text, it would expand
to two lines and the formatting would not go away
- split quoted and unquoted image case into separate regexps, since we can't
include a group reference inside a character set
- disallow spaces in the non-quoted case
- this should fix matching on images with other attributes again
- utf8/unicode is valid in the src string, provided we escape quotes
- and we escape when setting fields in the editor, leading to double escaping
if we do that
- and we strip quotes when adding
- make sure we default to last saved export location
- make sure we filter out backslash
- use fname not initial_path, because we're not passing in a path
- when answer not correct, show both the given and correct string in separate
markup. we use red/green for the given string to indicate what was correct,
but we use grey rather than red on the correct string to indicate what was
missing, as red is misleading
- colours can now be customized in css with .typeGood, .typeBad and
.typeMissing
- answer now shown in monospace so given/correct lines up; can be customized
with code#typeans
- do away with 'correct answer was' text that people didn't like
this means that copying&pasting images on linux/firefox will redownload the
image which is wasteful, but Windows users make up the majority of the
userbase
we were replacing spans with spaces during review but not during media check.
just strip the tags instead, which makes the media check consistent and
doesn't result in multiple identical answers
- allow creation of cloze deletion when note type not selected; warn with
tooltip. prevents selection from getting lost
- warn before adding cloze note type with no deletions