navigation API: resolve the finished promise

[atscott]

What is the issue with the HTML Standard?

In the navigation API's resolve the finished promise steps, it includes the following:

Resolve apiMethodTracker's committed promise with its committed-to entry.

Usually, notify about the committed-to entry has previously been called on apiMethodTracker, and so this will do nothing. However, in some cases resolve the finished promise is called directly, in which case this step is necessary.

I don't believe this is accurate and think the step and note should be removed. From what I can tell, resolve should never be called without the commit steps having already been run. If not, the committed-to entry would still be null unless there is some place that sets it without doing the other steps in notifying about the committed-to and I don't think that's the case.