Get rid of element.removeChild(element.firstChild)
usage (bug 1345253)
#8138
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.
Instead of just upstreaming the changes from bug 1345253 as-is, it seemed better to simply get rid of the loops altogether and use the same approach as in
PDFViewer
/PDFThumbnailViewer
.The PR also fixes an existing issue with
PDFOutlineViewer.reset
not actually resetting all the state it should.Fixes #8139.