Delete Firefox installation codebase
Review Request #9832 — Created March 25, 2018 and discarded
Since Firefox can install Chrome extensions directly, a seperate code base for Firefox is not required. Therefore I deleted the XPI code;
Try User test on Firefox and Chrome to make sure all features still works after the deletion.
Description | From | Last Updated |
---|---|---|
Typos/changes in description: noe -> not chrome -> Chrome Also, I'm not sure what "deleted most of them" means. Can … |
david | |
Testing done? |
david | |
Col: 17 'row' is already defined. |
reviewbot | |
The changes to this file seem unrelated to the intent of this review request. Please fix up this change to … |
david | |
I think we can avoid doing the UA string detection here, and instead use something like: if (!browser) { var … |
mike_conley | |
Let's call this callbackFn instead. |
mike_conley | |
I'm reasonably certain that the Firefox implementation of the API also can take a callback function, can it not? |
mike_conley | |
Let's call this callbackFun instead. |
mike_conley | |
Same as above, re: captureVisibleTab. |
mike_conley | |
As before, I think we can skip the UA detection here. |
mike_conley | |
Again, I'm reasonably sure that the Firefox implementation can take a callback as well, and only optionally returns a Promise. |
mike_conley | |
Same as above. Also, there are some general formatting things that you need to watch out for here (indentation, spacing … |
mike_conley | |
Same as before, re: UA detection |
mike_conley | |
Same as before, re: UA detection |
mike_conley | |
trailing whitespace |
mike_conley | |
Why is this needed? |
mike_conley | |
Busted indentation here, and some trailing whitespace |
mike_conley |
- Commit:
-
d4fadb3c02e3df7b83928089acc24d82d923d0195c658e6b95e4bc15f48524879b5f440229e4355d
Checks run (2 succeeded)
- Description:
-
~ Since Firefox can noe install chrome extensions directly, a seperate code base for Firefox is not required. Therefore I deleted most of them;
~ Since Firefox can not install Chrome extensions directly, a seperate code base for Firefox is not required. Therefore I deleted the XPI code;
- Testing Done:
-
+ Try User test on Firefox and Chrome to make sure all features still works after the deletion.
- Commit:
-
5c658e6b95e4bc15f48524879b5f440229e4355d188d2615fa8e939d2d78f317a4ee6cc325a43462
Checks run (2 succeeded)
- Commit:
-
188d2615fa8e939d2d78f317a4ee6cc325a4346223bd0572d5b040c365ca6ae402b504dd02fb0fe6
Checks run (2 timed out)
- Commit:
-
23bd0572d5b040c365ca6ae402b504dd02fb0fe62d476ce0a249f2cffe4ed89d75bc07e2e1354786
Checks run (2 timed out)
- Commit:
-
2d476ce0a249f2cffe4ed89d75bc07e2e135478668c43e1667ba3a4297ff286f140d62ad39c7771c
Checks run (2 timed out)
-
Hey Ridum,
Since Firefox can not install Chrome extensions directly
I think you mean "Since Firefox can install Chrome extensions directly".
I have a bunch of notes here, mainly around UA detection and some formatting / stylistic stuff. Also, I think we can probably get rid of the crx folder and move everything into the root folder, can we not? Or perhaps just have a generic "extension" folder?
-
I think we can avoid doing the UA string detection here, and instead use something like:
if (!browser) { var browser = chrome; }
-
-
I'm reasonably certain that the Firefox implementation of the API also can take a callback function, can it not?
-
-
-
-
Again, I'm reasonably sure that the Firefox implementation can take a callback as well, and only optionally returns a Promise.
-
Same as above. Also, there are some general formatting things that you need to watch out for here (indentation, spacing around braces, trailing whitespace).
-
-
-
-
-
- Description:
-
~ Since Firefox can not install Chrome extensions directly, a seperate code base for Firefox is not required. Therefore I deleted the XPI code;
~ Since Firefox can install Chrome extensions directly, a seperate code base for Firefox is not required. Therefore I deleted the XPI code;
- Commit:
-
68c43e1667ba3a4297ff286f140d62ad39c7771cdf7f385553c8faf2010574c6b805888760dd3ee9