|
|
Chromium Code Reviews|
Created:
4 years, 2 months ago by catmullings Modified:
3 years, 4 months ago CC:
chromium-reviews, chromium-apps-reviews_chromium.org, extensions-reviews_chromium.org Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionDeprecate --load-component-extension command line flag
The --load-component-extension is a powerful, yet dangerous flag that developers
have been using to load extensions (for details, see b615096).
This deprecation has been planned in two phases. First, support a
--disable-extensions-except flag, which disables all extensions that are not
specified, but treats the listed extensions as normal extensions
(landed as crrev.org/2166513002/).
Second, remove support for the --load-component-extension flag entirely, which
is this cl.
BUG=615096
Committed: https://crrev.com/1cc8fc7b0404e98ed920e13a0d5dca44aeac7b71
Cr-Commit-Position: refs/heads/master@{#436453}
Patch Set 1 #
Total comments: 2
Patch Set 2 : Small one-line fix #
Total comments: 4
Patch Set 3 : Addressed code review comments #Patch Set 4 : Rebase master #
Total comments: 1
Patch Set 5 : Rebase master #
Messages
Total messages: 45 (32 generated)
Description was changed from ========== Working implementation and test of --load-component-extension BUG=615096 ========== to ========== The --load-component-extension is a powerful, yet dangerous flag that developers have been using to load extensions (for details, see b615096). This deprecation has been planned in two phases. First, create a --disable-extensions-except flag, which disables all extensions that are not specified, but treats the listed extensions as normal extensions (landed as crrev.org/2166513002/). Second, remove support for the --load-component-extension flag entirely, which is this cl. BUG=615096 ==========
Description was changed from ========== The --load-component-extension is a powerful, yet dangerous flag that developers have been using to load extensions (for details, see b615096). This deprecation has been planned in two phases. First, create a --disable-extensions-except flag, which disables all extensions that are not specified, but treats the listed extensions as normal extensions (landed as crrev.org/2166513002/). Second, remove support for the --load-component-extension flag entirely, which is this cl. BUG=615096 ========== to ========== The --load-component-extension is a powerful, yet dangerous flag that developers have been using to load extensions (for details, see b615096). This deprecation has been planned in two phases. First, support a --disable-extensions-except flag, which disables all extensions that are not specified, but treats the listed extensions as normal extensions (landed as crrev.org/2166513002/). Second, remove support for the --load-component-extension flag entirely, which is this cl. BUG=615096 ==========
catmullings@chromium.org changed reviewers: + rdcronin@google.com
https://codereview.chromium.org/2389703005/diff/1/chrome/browser/extensions/e... File chrome/browser/extensions/extension_startup_browsertest.cc (right): https://codereview.chromium.org/2389703005/diff/1/chrome/browser/extensions/e... chrome/browser/extensions/extension_startup_browsertest.cc:310: class DeprecatedLoadComponentExtensionSwitchBrowserTest I essentially used the same class structure as the DisableExtensionsExceptBrowserTest below. Lmk if this type of duplication isn't good style.
catmullings@chromium.org changed reviewers: + rdevlin.cronin@chromium.org - rdcronin@google.com
The CQ bit was checked by catmullings@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
Please remember to wrap your title/commit descriptions to 72 chars for git friendliness. :) Also, it looks like one of the telemetry tests is failing. Let's reach out to the team about it to see if we can move them off it/remove the test. https://codereview.chromium.org/2389703005/diff/20001/chrome/browser/extensio... File chrome/browser/extensions/extension_startup_browsertest.cc (right): https://codereview.chromium.org/2389703005/diff/20001/chrome/browser/extensio... chrome/browser/extensions/extension_startup_browsertest.cc:310: class DeprecatedLoadComponentExtensionSwitchBrowserTest We don't always add a "this feature was properly removed" test, but I'm supportive of adding one in this case. But we can probably put a TODO(catmullings) to remove this in, say, M57 or so. https://codereview.chromium.org/2389703005/diff/20001/chrome/common/chrome_sw... File chrome/common/chrome_switches.cc (left): https://codereview.chromium.org/2389703005/diff/20001/chrome/common/chrome_sw... chrome/common/chrome_switches.cc:27: const char kAllowCrossOriginAuthPrompt[] = "allow-cross-origin-auth-prompt"; I'm guessing this was git cl format's doing? (Usually we don't change unrelated code because it can pollute the git blame history, but making the tool not do it is sometimes tricky.)
Description was changed from ========== The --load-component-extension is a powerful, yet dangerous flag that developers have been using to load extensions (for details, see b615096). This deprecation has been planned in two phases. First, support a --disable-extensions-except flag, which disables all extensions that are not specified, but treats the listed extensions as normal extensions (landed as crrev.org/2166513002/). Second, remove support for the --load-component-extension flag entirely, which is this cl. BUG=615096 ========== to ========== The --load-component-extension is a powerful, yet dangerous flag that developers have been using to load extensions (for details, see b615096). This deprecation has been planned in two phases. First, support a --disable-extensions-except flag, which disables all extensions that are not specified, but treats the listed extensions as normal extensions (landed as crrev.org/2166513002/). Second, remove support for the --load-component-extension flag entirely, which is this cl. BUG=615096 ==========
Description was changed from ========== The --load-component-extension is a powerful, yet dangerous flag that developers have been using to load extensions (for details, see b615096). This deprecation has been planned in two phases. First, support a --disable-extensions-except flag, which disables all extensions that are not specified, but treats the listed extensions as normal extensions (landed as crrev.org/2166513002/). Second, remove support for the --load-component-extension flag entirely, which is this cl. BUG=615096 ========== to ========== The --load-component-extension is a powerful, yet dangerous flag that developers have been using to load extensions (for details, see b615096). This deprecation has been planned in two phases. First, support a --disable-extensions-except flag, which disables all extensions that are not specified, but treats the listed extensions as normal extensions (landed as crrev.org/2166513002/). Second, remove support for the --load-component-extension flag entirely, which is this cl. BUG=615096 ==========
Patchset #3 (id:40001) has been deleted
On 2016/10/10 15:33:27, Devlin wrote: > Please remember to wrap your title/commit descriptions to 72 chars for git > friendliness. :) Done. > > Also, it looks like one of the telemetry tests is failing. Let's reach out to > the team about it to see if we can move them off it/remove the test. Sounds good! > > https://codereview.chromium.org/2389703005/diff/20001/chrome/browser/extensio... > File chrome/browser/extensions/extension_startup_browsertest.cc (right): > > https://codereview.chromium.org/2389703005/diff/20001/chrome/browser/extensio... > chrome/browser/extensions/extension_startup_browsertest.cc:310: class > DeprecatedLoadComponentExtensionSwitchBrowserTest > We don't always add a "this feature was properly removed" test, but I'm > supportive of adding one in this case. But we can probably put a > TODO(catmullings) to remove this in, say, M57 or so. > > https://codereview.chromium.org/2389703005/diff/20001/chrome/common/chrome_sw... > File chrome/common/chrome_switches.cc (left): > > https://codereview.chromium.org/2389703005/diff/20001/chrome/common/chrome_sw... > chrome/common/chrome_switches.cc:27: const char kAllowCrossOriginAuthPrompt[] > = "allow-cross-origin-auth-prompt"; > I'm guessing this was git cl format's doing? (Usually we don't change unrelated > code because it can pollute the git blame history, but making the tool not do it > is sometimes tricky.)
https://codereview.chromium.org/2389703005/diff/20001/chrome/browser/extensio... File chrome/browser/extensions/extension_startup_browsertest.cc (right): https://codereview.chromium.org/2389703005/diff/20001/chrome/browser/extensio... chrome/browser/extensions/extension_startup_browsertest.cc:310: class DeprecatedLoadComponentExtensionSwitchBrowserTest On 2016/10/10 15:33:26, Devlin wrote: > We don't always add a "this feature was properly removed" test, but I'm > supportive of adding one in this case. But we can probably put a > TODO(catmullings) to remove this in, say, M57 or so. Done. https://codereview.chromium.org/2389703005/diff/20001/chrome/common/chrome_sw... File chrome/common/chrome_switches.cc (left): https://codereview.chromium.org/2389703005/diff/20001/chrome/common/chrome_sw... chrome/common/chrome_switches.cc:27: const char kAllowCrossOriginAuthPrompt[] = "allow-cross-origin-auth-prompt"; On 2016/10/10 15:33:26, Devlin wrote: > I'm guessing this was git cl format's doing? (Usually we don't change unrelated > code because it can pollute the git blame history, but making the tool not do it > is sometimes tricky.) Done.
The CQ bit was checked by catmullings@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)
The CQ bit was checked by catmullings@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: win_chromium_compile_dbg_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_comp...)
The CQ bit was checked by catmullings@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by catmullings@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
No L-G-T-M from a valid reviewer yet. CQ run can only be started by full committers or once the patch has received an L-G-T-M from a full committer. Even if an L-G-T-M may have been provided, it was from a non-committer, _not_ a full super star committer. See http://www.chromium.org/getting-involved/become-a-committer Note that this has nothing to do with OWNERS files.
Description was changed from ========== The --load-component-extension is a powerful, yet dangerous flag that developers have been using to load extensions (for details, see b615096). This deprecation has been planned in two phases. First, support a --disable-extensions-except flag, which disables all extensions that are not specified, but treats the listed extensions as normal extensions (landed as crrev.org/2166513002/). Second, remove support for the --load-component-extension flag entirely, which is this cl. BUG=615096 ========== to ========== Deprecate --load-component-extension command line flag The --load-component-extension is a powerful, yet dangerous flag that developers have been using to load extensions (for details, see b615096). This deprecation has been planned in two phases. First, support a --disable-extensions-except flag, which disables all extensions that are not specified, but treats the listed extensions as normal extensions (landed as crrev.org/2166513002/). Second, remove support for the --load-component-extension flag entirely, which is this cl. BUG=615096 ==========
lgtm https://codereview.chromium.org/2389703005/diff/80001/chrome/browser/extensio... File chrome/browser/extensions/extension_startup_browsertest.cc (right): https://codereview.chromium.org/2389703005/diff/80001/chrome/browser/extensio... chrome/browser/extensions/extension_startup_browsertest.cc:310: // TODO(catmullings): Remove test in future chrome release, perhaps M57. let's make this maybe M59 now. :)
The CQ bit was checked by catmullings@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from rdevlin.cronin@chromium.org Link to the patchset: https://codereview.chromium.org/2389703005/#ps100001 (title: "Rebase master")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch.
Bot data: {"patchset_id": 100001, "attempt_start_ts": 1480977397238580,
"parent_rev": "4ac56e72b47b93e3fd64f5edbd4c18c237299bf1", "commit_rev":
"5473a61473ef6a88af4d8d6fc2700791b7d90752"}
Message was sent while issue was closed.
Description was changed from ========== Deprecate --load-component-extension command line flag The --load-component-extension is a powerful, yet dangerous flag that developers have been using to load extensions (for details, see b615096). This deprecation has been planned in two phases. First, support a --disable-extensions-except flag, which disables all extensions that are not specified, but treats the listed extensions as normal extensions (landed as crrev.org/2166513002/). Second, remove support for the --load-component-extension flag entirely, which is this cl. BUG=615096 ========== to ========== Deprecate --load-component-extension command line flag The --load-component-extension is a powerful, yet dangerous flag that developers have been using to load extensions (for details, see b615096). This deprecation has been planned in two phases. First, support a --disable-extensions-except flag, which disables all extensions that are not specified, but treats the listed extensions as normal extensions (landed as crrev.org/2166513002/). Second, remove support for the --load-component-extension flag entirely, which is this cl. BUG=615096 ==========
Message was sent while issue was closed.
Committed patchset #5 (id:100001)
Message was sent while issue was closed.
Description was changed from ========== Deprecate --load-component-extension command line flag The --load-component-extension is a powerful, yet dangerous flag that developers have been using to load extensions (for details, see b615096). This deprecation has been planned in two phases. First, support a --disable-extensions-except flag, which disables all extensions that are not specified, but treats the listed extensions as normal extensions (landed as crrev.org/2166513002/). Second, remove support for the --load-component-extension flag entirely, which is this cl. BUG=615096 ========== to ========== Deprecate --load-component-extension command line flag The --load-component-extension is a powerful, yet dangerous flag that developers have been using to load extensions (for details, see b615096). This deprecation has been planned in two phases. First, support a --disable-extensions-except flag, which disables all extensions that are not specified, but treats the listed extensions as normal extensions (landed as crrev.org/2166513002/). Second, remove support for the --load-component-extension flag entirely, which is this cl. BUG=615096 Committed: https://crrev.com/1cc8fc7b0404e98ed920e13a0d5dca44aeac7b71 Cr-Commit-Position: refs/heads/master@{#436453} ==========
Message was sent while issue was closed.
Patchset 5 (id:??) landed as https://crrev.com/1cc8fc7b0404e98ed920e13a0d5dca44aeac7b71 Cr-Commit-Position: refs/heads/master@{#436453}
Message was sent while issue was closed.
c.meldaa@gmail.com changed reviewers: + c.meldaa@gmail.com
Message was sent while issue was closed.
https://codereview.chromium.org/2389703005/diff/1/chrome/browser/extensions/e... File chrome/browser/extensions/extension_startup_browsertest.cc (right): https://codereview.chromium.org/2389703005/diff/1/chrome/browser/extensions/e... chrome/browser/extensions/extension_startup_browsertest.cc:310: class DeprecatedLoadComponentExtensionSwitchBrowserTest On 2016/10/04 23:05:23, catmullings wrote: > <font><font>V podstatě jsem použil stejnou třídu struktury jako DisableExtensionsExceptBrowserTest níže. </font><font>Lmk, pokud tento typ duplikace není dobrý styl. > </font></font> Done.
Message was sent while issue was closed.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
