Open
Bug 1247794
Opened 10 years ago
Updated 1 year ago
support persistent identifiers in chrome.downloads.*
Categories
(WebExtensions :: Compatibility, defect, P5)
WebExtensions
Compatibility
Tracking
(Not tracked)
NEW
People
(Reporter: aswan, Unassigned)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [downloads] triaged)
various methods in chrome.downloads use numeric identifiers for downloads that persist across reboots. It is unclear how many extensions rely on this, but it will require changes to the core FF download code to support...
https://developer.chrome.com/extensions/downloads
|
||
Updated•10 years ago
|
Priority: -- → P2
Whiteboard: [downloads] → [downloads] triaged
|
||
Updated•9 years ago
|
Assignee: nobody → mixedpuppy
|
|
||
Updated•9 years ago
|
Component: WebExtensions: Untriaged → WebExtensions: Request Handling
|
||
Updated•8 years ago
|
Assignee: mixedpuppy → nobody
Component: WebExtensions: Request Handling → WebExtensions: Compatibility
|
|
||
Updated•8 years ago
|
Depends on: webextensions-code-debt
|
|
||
Updated•8 years ago
|
Priority: P2 → P5
|
||
Updated•7 years ago
|
Product: Toolkit → WebExtensions
|
||
Updated•7 years ago
|
Blocks: webextensions-code-debt
No longer depends on: webextensions-code-debt
I just discovered I got bitten by this bug. It is quite sneaky because it will not be discovered when testing an extension in single sessions (e.g. using web-ext run).
While this is not yet fixed, might it make sense to at least update the browser compatibility table to show id as being only partially supported?
|
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•