|
|
Created:
3 years, 10 months ago by davidsac (gone - try alexmos) Modified:
3 years, 10 months ago CC:
chromium-reviews, pfeldman, devtools-reviews_chromium.org Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionCurrently, if a browser has one Devtools Chrome extension installed, all chrome extensions are given permission to be rendered in the same process as devtools. Instead, each individual extension should be granted permission for its origin.
This is intended to be part of a greater bug fix for implementing OOPIFs within Devtools Extensions correctly. See the bug below.
BUG=570483
Review-Url: https://codereview.chromium.org/2703963002
Cr-Commit-Position: refs/heads/master@{#452290}
Committed: https://chromium.googlesource.com/chromium/src/+/8bad2c7e2500efc916a03dc146c01909cd1a757a
Patch Set 1 #
Total comments: 2
Patch Set 2 : fix nit #Messages
Total messages: 29 (19 generated)
The CQ bit was checked by davidsac@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...
Description was changed from ========== change |GrantScheme| to |GrantOrigin| BUG=570483 ========== to ========== change |GrantScheme| to |GrantOrigin| BUG=570483 ==========
Description was changed from ========== change |GrantScheme| to |GrantOrigin| BUG=570483 ========== to ========== Currently, if a browser has one Devtools Chrome extension installed, all chrome extensions are given permission to be rendered in the same process as devtools. Instead, each individual extension should be granted permission for its origin. BUG=570483 ==========
Description was changed from ========== Currently, if a browser has one Devtools Chrome extension installed, all chrome extensions are given permission to be rendered in the same process as devtools. Instead, each individual extension should be granted permission for its origin. BUG=570483 ========== to ========== Currently, if a browser has one Devtools Chrome extension installed, all chrome extensions are given permission to be rendered in the same process as devtools. Instead, each individual extension should be granted permission for its origin. This is intended to be part of a greater bug fix for implementing OOPIFs within Devtools Extensions correctly. See the bug below. BUG=570483 ==========
davidsac@chromium.org changed reviewers: + alexmos@chromium.org, creis@chromium.org, nick@chromium.org
Hi Charlie and Nick, I've made a first attempt at the proposed solution for implementing a fix for OOPIFs within devtools Extensions. Please take a look and let me know what you think!
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: cast_shell_linux on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) chromeos_daisy_chromium_compile_only_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) chromium_presubmit on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL) linux_chromium_tsan_rel_ng on master.tryserver.chromium.linux (JOB_TIMED_OUT, no build URL)
lgtm https://codereview.chromium.org/2703963002/diff/1/chrome/browser/devtools/dev... File chrome/browser/devtools/devtools_ui_bindings.cc (right): https://codereview.chromium.org/2703963002/diff/1/chrome/browser/devtools/dev... chrome/browser/devtools/devtools_ui_bindings.cc:1271: url::Origin(extension.get()->url())); extension.get()->url() can be simplified to extension->url()
The CQ bit was checked by davidsac@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
Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
The CQ bit was checked by davidsac@chromium.org to run a CQ dry run
The nit has been fixed https://codereview.chromium.org/2703963002/diff/1/chrome/browser/devtools/dev... File chrome/browser/devtools/devtools_ui_bindings.cc (right): https://codereview.chromium.org/2703963002/diff/1/chrome/browser/devtools/dev... chrome/browser/devtools/devtools_ui_bindings.cc:1271: url::Origin(extension.get()->url())); On 2017/02/22 19:20:06, ncarter wrote: > extension.get()->url() > > can be simplified to > > extension->url() Done.
The nit has been fixed.
davidsac@chromium.org changed reviewers: + dgozman@chromium.org
Hi dgozman, Could you please review this changelist for OWNER approval?
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
lgtm
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 davidsac@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from nick@chromium.org Link to the patchset: https://codereview.chromium.org/2703963002/#ps20001 (title: "fix nit")
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": 20001, "attempt_start_ts": 1487807712890440, "parent_rev": "c59596d13ec0e105c72dd69661b8bcb505d9afa7", "commit_rev": "8bad2c7e2500efc916a03dc146c01909cd1a757a"}
Message was sent while issue was closed.
Description was changed from ========== Currently, if a browser has one Devtools Chrome extension installed, all chrome extensions are given permission to be rendered in the same process as devtools. Instead, each individual extension should be granted permission for its origin. This is intended to be part of a greater bug fix for implementing OOPIFs within Devtools Extensions correctly. See the bug below. BUG=570483 ========== to ========== Currently, if a browser has one Devtools Chrome extension installed, all chrome extensions are given permission to be rendered in the same process as devtools. Instead, each individual extension should be granted permission for its origin. This is intended to be part of a greater bug fix for implementing OOPIFs within Devtools Extensions correctly. See the bug below. BUG=570483 Review-Url: https://codereview.chromium.org/2703963002 Cr-Commit-Position: refs/heads/master@{#452290} Committed: https://chromium.googlesource.com/chromium/src/+/8bad2c7e2500efc916a03dc146c0... ==========
Message was sent while issue was closed.
Committed patchset #2 (id:20001) as https://chromium.googlesource.com/chromium/src/+/8bad2c7e2500efc916a03dc146c0... |