Make installer changes for dual browser extension on Windows
Categories
(Firefox :: Installer, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox121 | --- | fixed |
People
(Reporter: nipunshukla002, Assigned: nipunshukla002)
References
Details
(Whiteboard: [fidedi])
Attachments
(6 files, 1 obsolete file)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
107 bytes,
text/x-google-doc
|
Details |
This bug describes the changes that we want to make to enable the dual browser extension to work with Firefox. As this still needs to be reviewed by Legal, I've marked it confidential.
| Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Comment 2•2 years ago
|
||
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 3•2 years ago
|
||
Made it so that the installer will only register itself as the protocol handler if there isn't one registered already.
Made it so that the uninstaller only deregisters itself if it's the current protocol handler.
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
| Assignee | ||
Comment 5•2 years ago
|
||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 7•2 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/74bc36c16ea3
https://hg.mozilla.org/mozilla-central/rev/804fb6912077
Comment 8•2 years ago
|
||
| bugherder | ||
Comment 9•2 years ago
|
||
| bugherder | ||
Updated•2 years ago
|
Comment 10•2 years ago
|
||
Don't these new protocols re-introduce bug 384384?
Comment 11•2 years ago
|
||
Comment 12•2 years ago
|
||
Comment 13•2 years ago
|
||
Comment 14•2 years ago
|
||
(In reply to Masatoshi Kimura [:emk] from comment #10)
Don't these new protocols re-introduce bug 384384?
Based on my understanding of Bug 384384, the risk is that arbitrary numbers of parameters can be sent locally to the Firefox command line because of Internet Explorer. Internet Explorer is less of a factor now, and besides that, the code implemented in the below link only allows for one non-dashed argument to Firefox (only one argument without --) and that argument has to start with http: and https: after the Firefox protocol.
https://phabricator.services.mozilla.com/rBETA31e067248e3c5326ee178777c2939075b50f9cda
Description
•