FilesApp: Support available bytes in gear menu UI for DocumentsProvider

This change implements "volume-space-info" Chrome gear menu item when
there is availability of writable DocumentsProvider root(s) with given
authority.

It will enable ARC apps like Box, DropBox, etc. to show available bytes
vs. capacity bytes within the volume's gear menu.  If the root is not
writable or both available and capacity bytes columns are unbounded,
the menu item will remain hidden as before. If the root's available
bytes is provided by the DocumentsProvider but not capacity, "Available"
field in the UI will be populated but progress bar will stay hidden.

To prevent performance issues, only the requested root ID based on
authority will be queried synchronously by ContentProviderClient for
available bytes and capacity bytes since these root changes are not
always updated by the provider app via notifyChange. The counterpart
Android CL is http://ag/13490814.

BUG=953657
BUG=b:179332056
TEST=Tested manually with Android CL and verified using Box app.

Change-Id: Ifb28875fc06f3431e1dbe7d6be38ab59dc4082f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2695949
Reviewed-by: Josh Simmons <simmonsjosh@google.com>
Reviewed-by: Naoki Fukino <fukino@chromium.org>
Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Alan Ding <alanding@chromium.org>
Cr-Commit-Position: refs/heads/master@{#856185}
21 files changed
tree: d17853f004a58f1842772c74894b4aea0e63f88a
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.