[geckodriver] Do not decode and create a file from "addon" field when sending "Addon:Install" command
Categories
(Testing :: geckodriver, task, P3)
Tracking
(Not tracked)
People
(Reporter: Sasha, Unassigned)
References
Details
(Whiteboard: [need to wait until Firefox 115/128 ESR is no longer supported])
Attachments
(1 file)
While working on bug 1806135, I've noticed that when sending Addon:Install with addon property containing the base64 representation, geckodriver creates a local file, which is not accessible when a browser is running on an Android device. Similar to what we do for profiles, in case of working with Android we have to push created files to the actual device.
| Reporter | ||
Updated•1 year ago
|
| Reporter | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
| Reporter | ||
Comment 2•1 year ago
|
||
We decided that for add-on installation command to make it easier later to support WebDriver BiDi we should actually not decode addon field and create a file on the geckodriver side (since BiDi doesn't use geckodriver), we should rather just forward the field as it is and have all required logic in the shared module. So repurposing the bug for this.
During the review process it turned out that we cannot do such a change right now to not loose backward compatibility. We basically need bug 1927172 landed first, and then wait for it to be available in the next 140 ESR release.
Updated•1 year ago
|
We have to wait with the patch on this bug until we no longer support Firefox 128. This will basically be the case when Firefox 143 gets released which is around early September 2026.
We extended the support for 115 ESR until March 2026. So we should still wait a little bit longer.
Description
•