A bit more information: When we tried reproducing it in GVE and Fenix using dev tools (meaning, to navigate by inspecting a background tab) - it doesn't reproduce in Fenix either. So, speculating here, it might have to do with the way a new tab is opened in the background.
Bug 1678103 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
A bit more information: When we tried reproducing it in GVE and Fenix using dev tools (meaning, to navigate by inspecting a background tab) - it doesn't reproduce in Fenix either. So, speculating here, it might have to do with the way a new tab is opened in the background. I moved this to the Fenix component, but I think to really check which layer this bug is in, might be useful to try to reproduce in another GV powered browser that has ability to pen tabs in background - maybe the Reference Browser
A bit more information: When we tried reproducing it in GVE and Fenix using dev tools (meaning, to navigate by inspecting a background tab) - it doesn't reproduce in Fenix either. So, speculating here, it might have to do with the way a new tab is opened in the background. I moved this to the Fenix component, but I think to really check which layer this bug is in, might be useful to try to reproduce in another GV powered browser that has ability to pen tabs in background - maybe the Reference Browser. If the state of the tab is not handled correctly by the app - and we don't communicate to Gecko correctly re: the backgroundness of the tab, that might mess up the web APIs