Merge branch 'oplog-limits-buffered' into devel
Remove Function(...) in component OO due to CSP

Can't use what's effectively an "eval" and still be safe for restrictive Content Security Policies.  Hopefully we get a better way to make classes print nicely in the dev console in the future.
Add UI.renderWithData; test UI.{insert,render*}
Spacebars: Disallow non-initial `this` in paths

Apparently `../this` used to work as a synonym for `..` in Handlebars, but in Spacebars it actually would look for a property named `this`, which caused confusing breaking changes in apps.
Change {{> content}} to {{> UI.contentBlock}}

...and elseContent to UI.elseBlock.
Better error handling around a method call

- Make sure not to double-resolve a future (using two different
  techniques!)

- Try/finally cleanup some resources
Merge branch 'devel' into shark

# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
Let tags containing ':' self-close

They won't be rendered to HTML as self-closing, but that should be ok.

This is so that weird XML tags in SVG can be parsed.
Fix regression: don't optimize SVG in templates
Merge branch 'pr/1718' into shark
Better error for non-existent template inclusion
Nonreactive callback for range.removed code

When a range is removed, if the component instance has a destroyed callback
defined, updateTemplateInstance is called and the destroyed callback is called
in the context of the updated templateInstance. updateTemplateInstance calls
getComonentData() which can create a reactive dependency. This doesn't seem
necessary since we're removing the range.

The problem surfaced in iron-router in combination with using the {{#each
helper. The each helper is currently the only builtin that adds a destroyed
callback. If a previous layout used {{#each and a new layout rendered, the
previous range would be removed in the new computation. Then, if we updated the
data context, the dep would change and the entire new layout would be rendered
again :-(.

cc @tmeasday.
Merge pull request #1904 from EventedMind/make-removed-nonreactive

Put range.removed code in a Deps.nonreactive callback
Fix nested autoruns in Blaze rendering

Should address bugs where helpers fire more than expected, and also prevent wasted re-rendering of templates that are being destroyed anyway.

See: https://github.com/EventedMind/iron-router/issues/478
Improve Deps performance by not using _.bind
Remove unused Deps._makeNonreactive
Merge branch 'devel' into shark
Don't use jQuery's buildFragment

It's slow and the benefits are not obvious
Merge remote-tracking branch 'origin/devel' into login-hooks
Add comment linking to hackpad.