(In reply to juraj.masiar from comment #2) > I can't really tell, title sounds ok but the steps are confusing... I would close that one and keep this. > The STRs here should probably highlight that the extension performs a reload. I can close the other one to avoid duplicated but I think the STRs are still worth mentioning here, because they work with any extension, and don't require to wait for N seconds: - load any temporary webextension with aboutdebugging - click on inspect - click on reload twice - try to use the console > I was hoping this issue will be fixed by bug 1753048 but my comments there were somehow ignored :( Sorry about that, I focused on the initial report and it turns out the two issues were not related. The comments were not ignored on purpose but in general filing dedicated bugs is better.
Bug 1778951 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to juraj.masiar from comment #2) > I can't really tell, title sounds ok but the steps are confusing... I would close that one and keep this. > The STRs here should probably highlight that the extension performs a reload. I can close the other one to avoid duplicated but I think the STRs are still worth mentioning here, because they work with any extension, and don't require to wait for N seconds: - load any temporary webextension with a background script with aboutdebugging - click on inspect - click on reload twice - try to use the console > I was hoping this issue will be fixed by bug 1753048 but my comments there were somehow ignored :( Sorry about that, I focused on the initial report and it turns out the two issues were not related. The comments were not ignored on purpose but in general filing dedicated bugs is better.