Revert "File Handling multi launch"

This reverts commit bc3ef1ba9275bf83a408b2fe8b9169827625278e.

Reason for revert: Looks like the culprit for new failures of many
TwoClientWebAppsIntegrationTestMacWinLinux tests.

https://ci.chromium.org/ui/p/chromium/builders/ci/Mac10.14%20Tests/23414/overview

Original change's description:
> File Handling multi launch
>
> Translate an app launch with multiple files handled by separate
> file handlers into multiple launches (i.e. multiple windows),
> rather than failing the launch if no single file handler accepts
> all file types present.
>
> The behavior on each OS between when a user selects multiple files
> and a command line for the PWA is crafted is slightly different on
> each platform --- see doc for details. As such, this primarily
> affects Linux for now, but will be more impactful when the new
> manifest member is added that controls whether an app wants to
> handle many files or just one in each launched context.*
>
> *See document linked from bug for more details.
>
> Bug: 1304003
> Change-Id: Iff88f8dd9be11b31967f9037543fd57ba007ef3f
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3503850
> Commit-Queue: Evan Stade <estade@chromium.org>
> Reviewed-by: Daniel Murphy <dmurph@chromium.org>
> Reviewed-by: Nancy Wang <nancylingwang@chromium.org>
> Reviewed-by: Greg Thompson <grt@chromium.org>
> Reviewed-by: Peter Marshall <petermarshall@chromium.org>
> Reviewed-by: Alan Cutter <alancutter@chromium.org>
> Reviewed-by: Maggie Cai <mxcai@chromium.org>
> Reviewed-by: Jiewei Qian <qjw@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#984626}

Bug: 1304003
Change-Id: I22e7c3fcd28e00045bf3f25ac7f0eda241d972cd
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3545998
Auto-Submit: Fergal Daly <fergal@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Owners-Override: Fergal Daly <fergal@google.com>
Commit-Queue: Fergal Daly <fergal@chromium.org>
Cr-Commit-Position: refs/heads/main@{#984661}
24 files changed
tree: 28faf335f5d75939324658052b90f43b06c6354c
  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. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.

If you found a bug, please file it at https://crbug.com/new.