Consider removing gecko-only DataTransfer APIs
Categories
(Core :: DOM: Events, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox71 | --- | fixed |
People
(Reporter: nika, Assigned: annyG)
References
Details
(Keywords: dev-doc-complete, site-compat)
Attachments
(1 file)
Updated•8 years ago
|
Reporter | ||
Comment 1•7 years ago
|
||
Updated•6 years ago
|
Comment 2•5 years ago
|
||
We've had these behind prefs for about a year now (since bug 1453153) on nightly. Unfortunately, we removed the usecounters when we added the pref control, so it's not clear what usage looks like...
That said, have we run into any fallout in nightly?
Assignee | ||
Comment 3•5 years ago
|
||
Hi Boris, I am not aware about any bugs that arose from us disabling these APIs, i.e. I haven't been NI on any bugs related to this. I am assuming we can completely disable it for non-chrome code then?
Comment 4•5 years ago
|
||
I think it might be worth trying, yes. So just flip the pref on non-nightly?
Reporter | ||
Comment 5•5 years ago
|
||
Sounds like a plan!
Assignee | ||
Comment 6•5 years ago
|
||
Comment 8•5 years ago
|
||
bugherder |
Comment 9•5 years ago
|
||
Posted site compatibility note: https://www.fxsitecompat.dev/en-CA/docs/2019/non-standard-datatransfer-apis-have-been-removed/
Updated•5 years ago
|
Comment 10•5 years ago
|
||
MDN docs complete for this; see https://app.zenhub.com/workspaces/mdn-sprint-board-5ab3d23fd0f4ea53b0022a61/issues/mdn/sprints/2265#issuecomment-550415012 for the full details.
Let me know if you'd like to see any more changes made. Thanks!
Description
•