This is because when refreshing a SERP, the browser will load the current URI, which can be different due to redirects and History pushes. And so, the `currentURI` will change, from something generated by a `SearchEngine` to possibly a completely different URI. I suppose one way around this is if we know that the trigger is from a refresh, don't update the currentURI.
Bug 1802519 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This is because when refreshing a SERP, the browser will load the current URI, which can be different due to redirects and History pushes. And so, the `currentURI` will change, from something generated by a `SearchEngine` to possibly a completely different URI. I suppose one way around this is if we know that the trigger is from a refresh, don't update the originalURI.