- More neutral default for "get_option"
- Separate integration tests for checking persistence behavior

feedback should be shown when student returns to block.

The new setting is called "pb_hide_feedback_if_attempts_remain".

When set to True, Problem Builder blocks will not show global feedback
messages (as long as one or more attempts remain), and will hide
results (correct/incorrect icons) for Long Answer blocks.

OC-1387 Always show tooltips feedback if tips are present.

Ensure default theme is used if theme has not been customized

Problem Builder: Add instance-wide option to hide previous answers for MCQs

- Refactor: Take advantage of mixins from xblock-utils accessing xblock settings.

- Fix existing tests.
- Add unit tests for code that deals with instance-wide options.
- Add integration test for scenario where previous answers for MCQs are configured to be hidden.

MCQs are shown when users revisit them.

blocks works in both Apros and the LMS.

Fix exponential rerendering after hitting next button too many times.

Bump version.

Implement Django Migrations

Create Django migrations, deprecate South.

Step Builder: Explain review links to users

Fix flaky tests

And remove .travis.yml file.

Copied from https://github.com/django/django/pull/3121/files#diff-f6d1c75ec606389da5af6558bf57f171

See code comment for more info. Unfortunately, I wasn't able
to find anything better than time.sleep().

We would often see 'Broken pipe' errors pulluting the logs when running tests.
Broken pipe errors occur when browser aborts connection. It can be because
the browser was navigated to a different url before the current page finished
loading, but it could also be because it started downloading an image, but decided
that the image didn't change after loading part of it, and aborts the connection
to use the version from the cache.

The broken pipe errors are benign and are actually suppressed by default in Django 1.8.

The scrolling is not entirely precise, it's sometimes off by a pixel or two.
Increase the tolerance to 2 pixels.

Competing Evidence: Fix issues from client QA

The videos have to be resized after each step is displayed,
because they are sized to fit into their container at load time,
but since the container isn't visible at load time, the videos
end up with wrong dimensions.

Trigger video resize after displaying each step.

The scrollIntoView function can be called multiple times,
which resulted in multiple (10+) scroll animations getting queued.

After the first animation successfully scrolled to the top of the step,
the others kept running one by one. The animations weren't visible
because the element was already scrolled to its final position, but if
you tried manually scrolling down while the animations were still running,
the window would be scrolled right back up.