|
|
Chromium Code Reviews|
Created:
3 years, 11 months ago by eostroukhov Modified:
3 years, 11 months ago CC:
chromium-reviews, caseq+blink_chromium.org, lushnikov+blink_chromium.org, pfeldman+blink_chromium.org, apavlov+blink_chromium.org, devtools-reviews_chromium.org, blink-reviews, kozyatinskiy+blink_chromium.org Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
Description[DevTools] Pass the frame payload
Some frame information, like URL and security origin was lost because
frame payload object was not passed in the ctor. This fixes empty origin
on the "Clear storage" section on the Application tab.
BUG=678832
Review-Url: https://codereview.chromium.org/2610963005
Cr-Commit-Position: refs/heads/master@{#442426}
Committed: https://chromium.googlesource.com/chromium/src/+/ed73f79d6abbe1f7f09b0ba735c5aba03072197c
Patch Set 1 #Patch Set 2 : [DevTools] Pass the frame payload #
Total comments: 2
Patch Set 3 : [DevTools] Pass the frame payload #
Total comments: 2
Patch Set 4 : [DevTools] Pass the frame payload #
Total comments: 1
Patch Set 5 : [DevTools] Pass the frame payload #
Total comments: 11
Patch Set 6 : [DevTools] Pass the frame payload #
Total comments: 2
Patch Set 7 : [DevTools] Pass the frame payload #
Messages
Total messages: 43 (27 generated)
The CQ bit was checked by eostroukhov@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...
eostroukhov@chromium.org changed reviewers: + dgozman%chromium.org@gtempaccount.com, pfeldman@chromium.org
Please take a look, I don't have attached bug report - just an issue I hit looking at something else.
Please file a bug and associate this change with it. We might want to merge the fix if that is regression.
Description was changed from ========== [DevTools] Pass the frame payload Some frame information, like URL and security origin was lost because frame payload object was not passed in the ctor. This fixes empty origin on the "Clear storage" section on the Application tab. BUG=NONE ========== to ========== [DevTools] Pass the frame payload Some frame information, like URL and security origin was lost because frame payload object was not passed in the ctor. This fixes empty origin on the "Clear storage" section on the Application tab. BUG=678832 ==========
Done.
The CQ bit was checked by eostroukhov@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...
I updated the patch, please take another look. I added commit hash to the bug report.
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_...)
https://codereview.chromium.org/2610963005/diff/20001/third_party/WebKit/Sour... File third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js (right): https://codereview.chromium.org/2610963005/diff/20001/third_party/WebKit/Sour... third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js:206: this._securityOriginManager.setMainSecurityOrigin(frame.url); You are setting url in place of security origin.
The CQ bit was checked by eostroukhov@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...
Thank you for the review. I've updated the CL, please take another look. https://codereview.chromium.org/2610963005/diff/20001/third_party/WebKit/Sour... File third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js (right): https://codereview.chromium.org/2610963005/diff/20001/third_party/WebKit/Sour... third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js:206: this._securityOriginManager.setMainSecurityOrigin(frame.url); On 2017/01/06 18:45:19, pfeldman wrote: > You are setting url in place of security origin. Done.
https://codereview.chromium.org/2610963005/diff/40001/third_party/WebKit/Sour... File third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js (right): https://codereview.chromium.org/2610963005/diff/40001/third_party/WebKit/Sour... third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js:206: this._securityOriginManager.setMainSecurityOrigin(frame.securityOrigin); You already have "addedOrigin" and you should do that from under if (addedOrigin) I guess.
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 eostroukhov@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...
Thanks. Change was updated, please take another look. https://codereview.chromium.org/2610963005/diff/40001/third_party/WebKit/Sour... File third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js (right): https://codereview.chromium.org/2610963005/diff/40001/third_party/WebKit/Sour... third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js:206: this._securityOriginManager.setMainSecurityOrigin(frame.securityOrigin); On 2017/01/06 19:49:08, pfeldman wrote: > You already have "addedOrigin" and you should do that from under if > (addedOrigin) I guess. I joined the addSecurityOrigin and setMainSecurityOrigin
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
https://codereview.chromium.org/2610963005/diff/60001/third_party/WebKit/Sour... File third_party/WebKit/Source/devtools/front_end/sdk/SecurityOriginManager.js (right): https://codereview.chromium.org/2610963005/diff/60001/third_party/WebKit/Sour... third_party/WebKit/Source/devtools/front_end/sdk/SecurityOriginManager.js:47: removeSecurityOrigin(securityOrigin) { I don't think this counter makes sense - _navigate would clean up childFrames, but not update the securityorigin counters. What you should do instead is traverse frames every time they change and compare sets of origins.
The CQ bit was checked by eostroukhov@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...
I changed the logic so now it recomputes entire list of origins. This resulted in two cases when events were reshuffled: 1. Origin removed event is now fired after the navigation event, not before. 2. Origin removed event is now fired before each detached, they are no longer batched. Please take a look.
https://codereview.chromium.org/2610963005/diff/80001/third_party/WebKit/Sour... File third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js (right): https://codereview.chromium.org/2610963005/diff/80001/third_party/WebKit/Sour... third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js:136: this._updateSecurityOrigins(); You should unconditionally update origins. https://codereview.chromium.org/2610963005/diff/80001/third_party/WebKit/Sour... third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js:211: frame._remove(); You should update origins here as well. https://codereview.chromium.org/2610963005/diff/80001/third_party/WebKit/Sour... third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js:431: var securityOrigins = []; You should use Set here, otherwise you report same origin as added multiple times. https://codereview.chromium.org/2610963005/diff/80001/third_party/WebKit/Sour... third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js:651: this._model._updateSecurityOrigins(); You are calling this in a loop, I'd rather intercept higher level calls. https://codereview.chromium.org/2610963005/diff/80001/third_party/WebKit/Sour... File third_party/WebKit/Source/devtools/front_end/sdk/SecurityOriginManager.js (right): https://codereview.chromium.org/2610963005/diff/80001/third_party/WebKit/Sour... third_party/WebKit/Source/devtools/front_end/sdk/SecurityOriginManager.js:14: this._securityOrigins = new Set(); Please annotate type (Set of strings) https://codereview.chromium.org/2610963005/diff/80001/third_party/WebKit/Sour... third_party/WebKit/Source/devtools/front_end/sdk/SecurityOriginManager.js:29: updateSecurityOrigins(securityOrigins) { Please annotate securityOrigins type, should be Set of strings.
The CQ bit was checked by eostroukhov@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...
Updated, please consider. These changes resulted in further changes in the notifications order. https://codereview.chromium.org/2610963005/diff/80001/third_party/WebKit/Sour... File third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js (right): https://codereview.chromium.org/2610963005/diff/80001/third_party/WebKit/Sour... third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js:136: this._updateSecurityOrigins(); On 2017/01/09 20:06:13, pfeldman wrote: > You should unconditionally update origins. Done. https://codereview.chromium.org/2610963005/diff/80001/third_party/WebKit/Sour... third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js:431: var securityOrigins = []; On 2017/01/09 20:06:13, pfeldman wrote: > You should use Set here, otherwise you report same origin as added multiple > times. Done. https://codereview.chromium.org/2610963005/diff/80001/third_party/WebKit/Sour... third_party/WebKit/Source/devtools/front_end/sdk/ResourceTreeModel.js:651: this._model._updateSecurityOrigins(); On 2017/01/09 20:06:13, pfeldman wrote: > You are calling this in a loop, I'd rather intercept higher level calls. Done. https://codereview.chromium.org/2610963005/diff/80001/third_party/WebKit/Sour... File third_party/WebKit/Source/devtools/front_end/sdk/SecurityOriginManager.js (right): https://codereview.chromium.org/2610963005/diff/80001/third_party/WebKit/Sour... third_party/WebKit/Source/devtools/front_end/sdk/SecurityOriginManager.js:14: this._securityOrigins = new Set(); On 2017/01/09 20:06:13, pfeldman wrote: > Please annotate type (Set of strings) Done. https://codereview.chromium.org/2610963005/diff/80001/third_party/WebKit/Sour... third_party/WebKit/Source/devtools/front_end/sdk/SecurityOriginManager.js:29: updateSecurityOrigins(securityOrigins) { On 2017/01/09 20:06:13, pfeldman wrote: > Please annotate securityOrigins type, should be Set of strings. Done.
lgtm % nit https://codereview.chromium.org/2610963005/diff/100001/third_party/WebKit/Sou... File third_party/WebKit/Source/devtools/front_end/sdk/SecurityOriginManager.js (right): https://codereview.chromium.org/2610963005/diff/100001/third_party/WebKit/Sou... third_party/WebKit/Source/devtools/front_end/sdk/SecurityOriginManager.js:35: this._securityOrigins = new Set(securityOrigins); No need to wrap in a new set, it is already a set.
The CQ bit was checked by eostroukhov@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...
Updated, please take another look. https://codereview.chromium.org/2610963005/diff/100001/third_party/WebKit/Sou... File third_party/WebKit/Source/devtools/front_end/sdk/SecurityOriginManager.js (right): https://codereview.chromium.org/2610963005/diff/100001/third_party/WebKit/Sou... third_party/WebKit/Source/devtools/front_end/sdk/SecurityOriginManager.js:35: this._securityOrigins = new Set(securityOrigins); On 2017/01/09 20:34:47, pfeldman wrote: > No need to wrap in a new set, it is already a set. I don't trust API users... But I changed the code.
The CQ bit was unchecked by eostroukhov@chromium.org
The CQ bit was checked by eostroukhov@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from pfeldman@chromium.org Link to the patchset: https://codereview.chromium.org/2610963005/#ps120001 (title: "[DevTools] Pass the frame payload")
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": 120001, "attempt_start_ts": 1483999808043390,
"parent_rev": "c95c89bebf9003e535e609060cd19849ca22a19f", "commit_rev":
"ed73f79d6abbe1f7f09b0ba735c5aba03072197c"}
Message was sent while issue was closed.
Description was changed from ========== [DevTools] Pass the frame payload Some frame information, like URL and security origin was lost because frame payload object was not passed in the ctor. This fixes empty origin on the "Clear storage" section on the Application tab. BUG=678832 ========== to ========== [DevTools] Pass the frame payload Some frame information, like URL and security origin was lost because frame payload object was not passed in the ctor. This fixes empty origin on the "Clear storage" section on the Application tab. BUG=678832 Review-Url: https://codereview.chromium.org/2610963005 Cr-Commit-Position: refs/heads/master@{#442426} Committed: https://chromium.googlesource.com/chromium/src/+/ed73f79d6abbe1f7f09b0ba735c5... ==========
Message was sent while issue was closed.
Committed patchset #7 (id:120001) as https://chromium.googlesource.com/chromium/src/+/ed73f79d6abbe1f7f09b0ba735c5... |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
