Can you add another paragraph explaining what this means?

Can you add another paragraph explaining what this means?

There's an extra blank line here.

This can use an ES6 template string.

Add spaces after commas here.

Instead of creating a variable for this, let's just define the fat arrow function inline:

parsed.load((metadata, html) =>
    this._reloadFromUpdate(entry, metadata, html));

Your editor completely reformatted this file to add indentation. Please revert the changes here.

Same with this file.

Add a trailing comma here. Let's also name the function _onToggleCollapseMouseover

Add a space between ) and {

This needs additional spaces:

Between if and (
Between ) and {

Use single quotes here.

=== will result in a bool. We don't need the ? true : false

This needs spaces like the if above.

This file got unwanted indentation.

An unwanted space was added at the beginning of this line.

The numbers on the names model, model2, view1, etc. don't really add anything useful, and they're all scoped to the test body anyway. Since we're just instantiating one per test, let's just call them model and view.

This can be const (we only assign to the name once). Same in other test cases.

Some more blank lines in here might make it a little more readable. We can also skip creating a variable for $collapseButton because we only use it once.

This looks great! I have suggestions to bring it up to our in-house standards, and a way to better generalize the conditional content loading part. Once fixed up, I think we'll be able to get this into 5.0!

"give" isn't a typical term used for this kind of function. A better one might be "fetch". How about calling this fetchEntryUpdates?

urlQueryStr is checking whether urlQuery has anything in it, but we're setting it to something immediately before. We probably can simplify this quite a bit by replacing all this code with:

const typeID = entry.get('typeID');
const urlQueryStr = `entries=${typeID}:${entry.id}`;


Nice and simple. No need to join the array, because we only ever have the one entry.

I think this function is likely to be more for internal use, so I'd suggest making it private (prefix with a _ and group it with other private functions).

EntryView shouldn't know what kind of subclasses there will be. In fact, extensions can provide whole new types of entries, which may want to load based on their own logic.
I'd suggest instead keeping state on the model indicating if the entry has been loaded, which would be part of the initial model data on the page. If loaded, have this function do nothing. If not loaded, load it.
And actually, given that the state would be in the model, and the operation that loads the updates is also in the model, I think this function would be better off in the model. Based on how we often name things, maybe call it ensureContentLoaded. This communicates that the function will load the content if it's needed (and otherwise do nothing — it just ensures that we end up with content one way or another in the end).

Based on our naming conventions, this should be templateWithoutBody. Likewise, below should be templateWithBody.

There's an extra sapce at the end of the class list.

Here, too.

And in these spots.

Can you add a blank line between these?

Extra space at the end of the string.

There are extra blank lines at the end of this file. Can you get rid of those?

Can you reorder this to be in alphabetical order? Should be before issueSummaryTableViewTests.

Since you're adding a new block tag, you'll need to indent all the block tags inside by one.
For Django templates, we'd do this like:

{% if not entry.collapsed %}
{%  if review.body_top ... %}
{%   blah blah %}
...
{%  endif %}
{% endif %}