Show ExtensionID->OriginSyncStatus in syncfs-internals WebUI.
BUG=244067
TEST=Manual
Sign into Chrome
Start any SyncFS application
Go to chrome://syncfs-internals, click on Extension Status tab
You should see at lease one extension along with its sync status.
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=206351
PTAL. It's about the same as before but now uses the landed DriveFileSyncService.GetOriginStatusMap() function. Updated ...
7 years, 6 months ago
(2013-06-07 05:52:46 UTC)
#1
PTAL. It's about the same as before but now uses the landed
DriveFileSyncService.GetOriginStatusMap() function.
Updated screenshot attached to the bug issue.
nhiroki
Looks good. https://codereview.chromium.org/16398011/diff/2003/chrome/browser/resources/sync_file_system_internals/extension_statuses.html File chrome/browser/resources/sync_file_system_internals/extension_statuses.html (right): https://codereview.chromium.org/16398011/diff/2003/chrome/browser/resources/sync_file_system_internals/extension_statuses.html#newcode12 chrome/browser/resources/sync_file_system_internals/extension_statuses.html:12: nit: Can you remove this blank line? ...
7 years, 6 months ago
(2013-06-07 06:31:25 UTC)
#2
+bauerb for chrome/browser/resources/sync_file_system_internals_resources.grd OWNERS review. Please take a look at actual code too if you ...
7 years, 6 months ago
(2013-06-07 06:48:13 UTC)
#4
+bauerb for chrome/browser/resources/sync_file_system_internals_resources.grd
OWNERS review.
Please take a look at actual code too if you have time. Our team has OWNERS file
ownership for the /sync_file_system_internals subdirectories now but an extra
review is also welcome.
Thanks!
nhiroki
+tzik@ for double checking.
7 years, 6 months ago
(2013-06-07 10:34:03 UTC)
#5
+tzik@ for double checking.
Bernhard Bauer
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/sync_file_system_internals/extension_statuses.js File chrome/browser/resources/sync_file_system_internals/extension_statuses.js (right): https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/sync_file_system_internals/extension_statuses.js#newcode11 chrome/browser/resources/sync_file_system_internals/extension_statuses.js:11: function extensionStatuses() { Class names should start upper-case. https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/sync_file_system_internals/extension_statuses.js#newcode55 ...
7 years, 6 months ago
(2013-06-07 10:44:46 UTC)
#6
7 years, 6 months ago
(2013-06-10 02:41:17 UTC)
#7
lgtm
calvinlo
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/sync_file_system_internals/extension_statuses.js File chrome/browser/resources/sync_file_system_internals/extension_statuses.js (right): https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/sync_file_system_internals/extension_statuses.js#newcode11 chrome/browser/resources/sync_file_system_internals/extension_statuses.js:11: function extensionStatuses() { On 2013/06/07 10:44:46, Bernhard Bauer wrote: ...
7 years, 6 months ago
(2013-06-10 05:15:45 UTC)
#8
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/...
File chrome/browser/resources/sync_file_system_internals/extension_statuses.js
(right):
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/...
chrome/browser/resources/sync_file_system_internals/extension_statuses.js:11:
function extensionStatuses() {
On 2013/06/07 10:44:46, Bernhard Bauer wrote:
> Class names should start upper-case.
Done.
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/...
chrome/browser/resources/sync_file_system_internals/extension_statuses.js:55:
document.addEventListener('DOMContentLoaded', main);
On 2013/06/07 10:44:46, Bernhard Bauer wrote:
> You could directly add getExtensionStatuses here.
Done.
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/...
chrome/browser/resources/sync_file_system_internals/extension_statuses.js:56:
return new extensionStatuses;
On 2013/06/07 10:44:46, Bernhard Bauer wrote:
> Do you actually need an instance of this class here? You could directly
declare
> a static method ExtensionStatuses.onGetExtensionStatuses and call that.
You're right, this could just be an exported static function. I originally
wanted to do that but my TL insisted before (for sync_service.js) that a whole
object be returned. Since that sync_service.js already declares functions using
the prototyping syntax and returns whole objects, I think it's good to keep this
the same way so all the. js files have the same style?
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/...
File chrome/browser/resources/sync_file_system_internals_resources.grd (right):
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/...
chrome/browser/resources/sync_file_system_internals_resources.grd:15: <include
name="IDR_SYNC_FILE_SYSTEM_INTERNALS_EXTENSION_STATUSES_JS"
file="sync_file_system_internals/extension_statuses.js" type="BINDATA" />
On 2013/06/07 10:44:46, Bernhard Bauer wrote:
> It probably would make sense to add the same OWNERS as
> chrome/browser/resources/sync_file_system_internals/ for this file.
Done. I've added per-file sync_file_system_internals.*=tzik@chromium.org to give
ownership to my teammate who should be the final owner of
sync_file_system_internals/
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/ui/webui/s...
File
chrome/browser/ui/webui/sync_file_system_internals/extension_statuses_handler.h
(right):
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/ui/webui/s...
chrome/browser/ui/webui/sync_file_system_internals/extension_statuses_handler.h:23:
virtual void RegisterMessages() OVERRIDE;
On 2013/06/07 10:44:46, Bernhard Bauer wrote:
> Can you add a comment that states what interface this implements?
Done.
7 years, 6 months ago
(2013-06-10 13:42:37 UTC)
#12
On 2013/06/10 05:15:45, calvinlo wrote:
>
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/...
> File chrome/browser/resources/sync_file_system_internals/extension_statuses.js
> (right):
>
>
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/...
> chrome/browser/resources/sync_file_system_internals/extension_statuses.js:11:
> function extensionStatuses() {
> On 2013/06/07 10:44:46, Bernhard Bauer wrote:
> > Class names should start upper-case.
>
> Done.
>
>
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/...
> chrome/browser/resources/sync_file_system_internals/extension_statuses.js:55:
> document.addEventListener('DOMContentLoaded', main);
> On 2013/06/07 10:44:46, Bernhard Bauer wrote:
> > You could directly add getExtensionStatuses here.
>
> Done.
>
>
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/...
> chrome/browser/resources/sync_file_system_internals/extension_statuses.js:56:
> return new extensionStatuses;
> On 2013/06/07 10:44:46, Bernhard Bauer wrote:
> > Do you actually need an instance of this class here? You could directly
> declare
> > a static method ExtensionStatuses.onGetExtensionStatuses and call that.
>
> You're right, this could just be an exported static function. I originally
> wanted to do that but my TL insisted before (for sync_service.js) that a whole
> object be returned. Since that sync_service.js already declares functions
using
> the prototyping syntax and returns whole objects, I think it's good to keep
this
> the same way so all the. js files have the same style?
I think what he's suggesting is doing something like following, which is
slightly different from your previous code.
(@bauerb please let me know if I'm wrong)
ExtensionStatuses.onGetExtensionStatuses = function(...) { ... };
document.addEventListener('DOMContentLoaded', getExtensionStatuses);
return ExtensionStatuses;
})();
And I agree that not creating an instance is better than what I suggested.
Anyway either way (keeping it as is or revising it to use static methods) works
for me.
>
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/...
> File chrome/browser/resources/sync_file_system_internals_resources.grd
(right):
>
>
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/resources/...
> chrome/browser/resources/sync_file_system_internals_resources.grd:15: <include
> name="IDR_SYNC_FILE_SYSTEM_INTERNALS_EXTENSION_STATUSES_JS"
> file="sync_file_system_internals/extension_statuses.js" type="BINDATA" />
> On 2013/06/07 10:44:46, Bernhard Bauer wrote:
> > It probably would make sense to add the same OWNERS as
> > chrome/browser/resources/sync_file_system_internals/ for this file.
>
> Done. I've added per-file
mailto:sync_file_system_internals.*=tzik@chromium.org to give
> ownership to my teammate who should be the final owner of
> sync_file_system_internals/
>
>
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/ui/webui/s...
> File
>
chrome/browser/ui/webui/sync_file_system_internals/extension_statuses_handler.h
> (right):
>
>
https://codereview.chromium.org/16398011/diff/21001/chrome/browser/ui/webui/s...
>
chrome/browser/ui/webui/sync_file_system_internals/extension_statuses_handler.h:23:
> virtual void RegisterMessages() OVERRIDE;
> On 2013/06/07 10:44:46, Bernhard Bauer wrote:
> > Can you add a comment that states what interface this implements?
>
> Done.
calvinlo
I rebased and then fixed up the JavaScript based on the given suggestion. Thanks for ...
7 years, 6 months ago
(2013-06-11 14:34:15 UTC)
#13
I rebased and then fixed up the JavaScript based on the given suggestion. Thanks
for that. Please also note that I added a refresh button to make it easier for
me to manually test. I manually tested the latest version just to make sure this
works, sorry about the casing typo before.
https://codereview.chromium.org/16398011/diff/51004/chrome/browser/ui/webui/s...
File
chrome/browser/ui/webui/sync_file_system_internals/extension_statuses_handler.cc
(right):
https://codereview.chromium.org/16398011/diff/51004/chrome/browser/ui/webui/s...
chrome/browser/ui/webui/sync_file_system_internals/extension_statuses_handler.cc:53:
web_ui()->CallJavascriptFunction("ExtensionStatuses.onGetExtensionStatuses",
On 2013/06/10 12:46:35, Bernhard Bauer wrote:
> Wait, you're still exporting a variable called "extensionStatuses" (lower
case).
> Does this work?
Sorry typo. Fixed.
calvinlo
Sorry to bug you again Bernhard, just wondering if you wanted to take a look ...
7 years, 6 months ago
(2013-06-12 10:04:15 UTC)
#14
Sorry to bug you again Bernhard, just wondering if you wanted to take a look at
this again before I try it in the CQ. I have enough owners to cover all the
patch files but I wanted to respect your original review and get your LGTM
before putting in the final version.
Thanks.
Bernhard Bauer
https://codereview.chromium.org/16398011/diff/100001/chrome/browser/resources/sync_file_system_internals/extension_statuses.js File chrome/browser/resources/sync_file_system_internals/extension_statuses.js (right): https://codereview.chromium.org/16398011/diff/100001/chrome/browser/resources/sync_file_system_internals/extension_statuses.js#newcode8 chrome/browser/resources/sync_file_system_internals/extension_statuses.js:8: var extensionStatuses = (function() { Sorry if I'm being ...
7 years, 6 months ago
(2013-06-12 10:53:31 UTC)
#15
Issue 16398011: Show ExtensionID->OriginSyncStatus in syncfs-internals WebUI
(Closed)
Created 7 years, 6 months ago by calvinlo
Modified 7 years, 6 months ago
Reviewers: nhiroki, Bernhard Bauer, tzik
Base URL: svn://svn.chromium.org/chrome/trunk/src
Comments: 27