The default bug view has changed. See this FAQ.

Implement tabs.discard method

NEW
Unassigned

Status

()

Toolkit
WebExtensions: Frontend
P3
normal
4 months ago
23 days ago

People

(Reporter: kernp25, Unassigned)

Tracking

(Depends on: 1 bug)

unspecified
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [tabs] triaged)

(Reporter)

Description

4 months ago
https://developer.chrome.com/extensions/tabs#method-discard

Updated

4 months ago
Depends on: 1284886

Updated

4 months ago
Status: UNCONFIRMED → NEW
Component: WebExtensions: Untriaged → WebExtensions: Frontend
Ever confirmed: true
Whiteboard: [tabs]

Updated

4 months ago
Summary: add chrome.tabs.discard method → Implement tabs.discard method

Updated

3 months ago
Priority: -- → P3
Whiteboard: [tabs] → [tabs] triaged

Updated

3 months ago
Duplicate of this bug: 1325484

Updated

3 months ago
webextensions: --- → +

Updated

3 months ago
Duplicate of this bug: 1270784

Updated

2 months ago
Duplicate of this bug: 1333047

Updated

2 months ago
See Also: → bug 1333046

Comment 4

2 months ago
Do we also want a dedicated method to restore tabs again (use case e.g. https://addons.mozilla.org/en-US/android/addon/tabpreloader/), or just allow e.g. the reload method to handle that case (which might or might not still require some code changes to correctly restore unloaded tabs)?

Comment 5

2 months ago
No, there's a corresponding tab `discarded` property that they should be able to set via `tabs.update` if we want to support that functionality. I'm frankly annoyed that even this method exists, rather than just the ability to set that property via `tabs.update` in the first place. I'm considering just implementing it as a compatibility stub that calls `tabs.update`.

Comment 6

2 months ago
I've got no real experience of that API, so thanks very much for the answer, sounds okay.
You need to log in before you can comment on or make changes to this bug.