Update chrome/chromium migrator due to location change
Categories
(Firefox :: Migration, task, P3)
Tracking
()
People
(Reporter: jaws, Unassigned)
Details
https://bugs.chromium.org/p/chromium/issues/detail?id=1173622 is changing cookie storage in Chromium. We will need to support both the current and the new location as there will be a mix of clients for some time.
Tim, can you help this get prioritized?
|
||
Comment 1•3 years ago
|
||
:jaws, yeah I can do that. Keeping NI open for now.
|
|
||
Comment 2•3 years ago
|
||
Hey Gijs, I see this work falls under your module so I think you would have better success knowing what the priority of this work is.
Feel free to kick back if my information is incorrect.
|
||
Comment 3•3 years ago
|
||
(In reply to Tim Giles [:tgiles] from comment #2)
Hey Gijs, I see this work falls under your module so I think you would have better success knowing what the priority of this work is.
Feel free to kick back if my information is incorrect.
Doing this is not trivial, so I don't think anyone on the desktop teams will pick it up unless it's prioritized by product.
Related, I have in the past thought that we should just drop support for importing cookies; they usually don't transfer well anyway.
Also, I think Chrome cookie import is probably broken for modern Chrome anyway, because we have bug 1163165 and friends on file, so any encrypted cookies don't get decrypted anyway, I think? So I expect this shouldn't be high-prio. Does that sound right?
|
|
||
Comment 4•3 years ago
|
||
I mean, the priority seems right to me.
Forwarding NI to :jaws for awareness. Just to be clear, the password manager team does not own this component and its not on our roadmap to do any work for this component. I say this because I was (and am) a bit confused why I got called to help make a priority decision about this work.
|
Reporter | |
Comment 5•3 years ago
|
||
Sorry Tim, for some reason I thought you were owning migrators now.
|
|
Reporter | |
Updated•3 years ago
|
Description
•