Open Bug 1762977 Opened 3 years ago Updated 2 years ago

Support tabs.MAX_CAPTURE_VISIBLE_TAB_CALLS_PER_SECOND

Categories

(WebExtensions :: Compatibility, enhancement, P5)

Product:
WebExtensions
Component:
Compatibility
Type:
enhancement

Tracking

(Not tracked)

People

(Reporter: kernp25, Unassigned)

References

(
URL
)

Details

Chrome has a new MAX_CAPTURE_VISIBLE_TAB_CALLS_PER_SECOND property.

The maximum number of times that captureVisibleTab can be called per second. captureVisibleTab is expensive and should not be called too often.

Flags: needinfo?(mixedpuppy)
Flags: needinfo?(mixedpuppy)
Whiteboard: [design-decision-needed]

probably just let this happen in triage

Whiteboard: [design-decision-needed]

There are so many ways for API calls to be expensive. Not sure if limiting the number of captureVisibleTabs calls to 2 would be the best way to go about this...

I'll link it to the bug where captureVisibleTabs's implementation is revisited, to increase the chance of making a decision about this bug.

See Also: → 1800421
Severity: -- → N/A
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.