Remove unnecessary state change in IDBTransaction::abort()
#466
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As far as I can tell, this line about changing the transaction's state to
inactiveuponabort()is non-observable and superfluous. The reason it's superfluous is because it's immediately followed by the "abort a transaction" steps, which change the state to "finished" on step 3, and steps 1-2 do not contain user-observable hooks (e.g. errors, listeners, etc.):Looking at the various browser implementations, it seems that they already ignore this step in practice:
AbortInternalwhich immediately setsmReadyStateto "finished".abortInternal(). It doesn't seem to set the state toinactiveduring this process.StartAbortingwhich also doesn't seem to set the state toinactive.The exception I can find is Ladybird, which does set the state to
inactive, but then immediately sets the state tofinishedwhich seems to illustrate that theinactivestep is unnecessary.The following tasks have been completed:
Implementation commitment:
Preview | Diff