User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0 Build ID: 20180322152034 Steps to reproduce: When using the `browser.tabs.discard` WebExtension API, it is possible that tabs end up in a state `{ discarded: true, state: 'loading', }`. Besides being semantically incorrect (discarded tabs aren't loading), this also causes the tab load indicator to keep rotating (or whatever movement it does now). The tab stays in that state until it is undated in some way. This only happens sporadically when closing tabs with the attached extension, which I am currently porting, installed. The extension detects the tab close and activates a loaded tab to be focused next, to avoid loading discarede (or not restored) tabs. Due to the asynchronicity of the `browser.tabs` API, this may sometimes/often happens too late and a discarded tab is loaded. The extension will then rapid-fire `tabs.discard` and `tabs.unpdate( , { active: true, })` calls to stop the loading. I will attach a sequence of actions and log messages that ended up with a `{ discarded: true, state: 'loading', }` tab in the next comment. Actual results: `browser.tabs.discard` leaves the tab in a state `{ discarded: true, state: 'loading', }`. Expected results: I think the tabs `status` should be `'complete'` for `discarded` tabs. Or `'discarded'`, but that would probably be backwards-incompatible.

The sequence of steps taken should be clear from the console output: - tabs [1..6] were open (some not restored, some already unloaded) - tab 7 was opened - tab 5 was closed - tab 7 was closed

Should probably be state: 'complete' as OP mentioned, but at the very least we should ensure that discarding tabs removes the tab throbber.