|
|
Chromium Code Reviews|
Created:
4 years, 4 months ago by Pete Williamson Modified:
4 years, 4 months ago CC:
chromium-reviews, romax+watch_chromium.org, fgorski+watch_chromium.org, dewittj+watch_chromium.org, petewil+watch_chromium.org, chili+watch_chromium.org, dimich+watch_chromium.org Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionRemove the GetStatus() call from SavePageRequest.
We are moving to a new system of storing a status field. This removes
code associated with the old way.
BUG=610521
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
Committed: https://crrev.com/ae875419ff203324cd94c335695a7f9c0081e197
Cr-Commit-Position: refs/heads/master@{#410227}
Patch Set 1 #Patch Set 2 : CR feedback from DougArnett and Chili #
Total comments: 1
Patch Set 3 : Undo the fix for closure since we put status back. #
Messages
Total messages: 29 (11 generated)
petewil@chromium.org changed reviewers: + chili@chromium.org, fgorski@chromium.org
To make sure we don't break closure, can you update the typedef here? https://cs.chromium.org/chromium/src/chrome/browser/resources/offline_pages/o... Also, the internals page currently explicitly shows status (https://cs.chromium.org/chromium/src/chrome/browser/resources/offline_pages/o...) You might want to remove that from the HTML and JS (https://cs.chromium.org/chromium/src/chrome/browser/resources/offline_pages/o...)
dougarnett@chromium.org changed reviewers: + dougarnett@chromium.org
lgtm
On 2016/08/04 00:14:06, chili wrote: > To make sure we don't break closure, can you update the typedef here? > https://cs.chromium.org/chromium/src/chrome/browser/resources/offline_pages/o... > > Also, the internals page currently explicitly shows status > (https://cs.chromium.org/chromium/src/chrome/browser/resources/offline_pages/o...) > You might want to remove that from the HTML and JS > (https://cs.chromium.org/chromium/src/chrome/browser/resources/offline_pages/o...) Status is about to return, but in a different form. So, my plan is to leave the status field blank for now, and put a value back into it early next week. Is that OK, or would you prefer that I remove the field in the meantime?
On 2016/08/04 00:20:36, Pete Williamson wrote: > On 2016/08/04 00:14:06, chili wrote: > > To make sure we don't break closure, can you update the typedef here? > > > https://cs.chromium.org/chromium/src/chrome/browser/resources/offline_pages/o... > > > > Also, the internals page currently explicitly shows status > > > (https://cs.chromium.org/chromium/src/chrome/browser/resources/offline_pages/o...) > > You might want to remove that from the HTML and JS > > > (https://cs.chromium.org/chromium/src/chrome/browser/resources/offline_pages/o...) > > Status is about to return, but in a different form. So, my plan is to leave the > status field blank for now, and put a value back into it early next week. Is > that OK, or would you prefer that I remove the field in the meantime? You could populate it with a hard coded "Available" for now maybe
On 2016/08/04 00:26:33, dougarnett wrote: > On 2016/08/04 00:20:36, Pete Williamson wrote: > > On 2016/08/04 00:14:06, chili wrote: > > > To make sure we don't break closure, can you update the typedef here? > > > > > > https://cs.chromium.org/chromium/src/chrome/browser/resources/offline_pages/o... > > > > > > Also, the internals page currently explicitly shows status > > > > > > (https://cs.chromium.org/chromium/src/chrome/browser/resources/offline_pages/o...) > > > You might want to remove that from the HTML and JS > > > > > > (https://cs.chromium.org/chromium/src/chrome/browser/resources/offline_pages/o...) > > > > Status is about to return, but in a different form. So, my plan is to leave > the > > status field blank for now, and put a value back into it early next week. Is > > that OK, or would you prefer that I remove the field in the meantime? > > You could populate it with a hard coded "Available" for now maybe Yes, I would vote for hard coding it to some string (or even setting to empty string). Not having it at all means the page might not render properly (with closure, and calling <obj>.status errors out with 'no such method')
Description was changed from ========== Remove the GetStatus() call from SavePageRequest. We are moving to a new system of storing a status field. This removes code associated with the old way. BUG=610521 ========== to ========== Remove the GetStatus() call from SavePageRequest. We are moving to a new system of storing a status field. This removes code associated with the old way. BUG=610521 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation ==========
Added string hardcoded to Available, changed definition for Closure.
lgtm with minor comment sorry about the confusion! https://codereview.chromium.org/2209993002/diff/20001/chrome/browser/resource... File chrome/browser/resources/offline_pages/offline_internals_browser_proxy.js (left): https://codereview.chromium.org/2209993002/diff/20001/chrome/browser/resource... chrome/browser/resources/offline_pages/offline_internals_browser_proxy.js:22: * status: string, Oh, sorry... if you're going to leave status as is, you will want to keep this line. I suggested to remove this if we were going to remove everything (the change as is will make the closure compiler fail)
The CQ bit was checked by petewil@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from dougarnett@chromium.org, chili@chromium.org Link to the patchset: https://codereview.chromium.org/2209993002/#ps40001 (title: "Undo the fix for closure since we put status back.")
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
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...)
petewil@chromium.org changed reviewers: + bauerb@chromium.org
+bauerb - Please look at changes to offline_internals_ui.cc
lgtm
The CQ bit was checked by petewil@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: android_clang_dbg_recipe on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/android_clan...) cast_shell_android on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/cast_shell_a...) linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)
The CQ bit was checked by petewil@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Committed patchset #3 (id:40001)
Message was sent while issue was closed.
Description was changed from ========== Remove the GetStatus() call from SavePageRequest. We are moving to a new system of storing a status field. This removes code associated with the old way. BUG=610521 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation ========== to ========== Remove the GetStatus() call from SavePageRequest. We are moving to a new system of storing a status field. This removes code associated with the old way. BUG=610521 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Committed: https://crrev.com/ae875419ff203324cd94c335695a7f9c0081e197 Cr-Commit-Position: refs/heads/master@{#410227} ==========
Message was sent while issue was closed.
Patchset 3 (id:??) landed as https://crrev.com/ae875419ff203324cd94c335695a7f9c0081e197 Cr-Commit-Position: refs/heads/master@{#410227} |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
