Remove DCHECK expecting at most one import assertion We've decided to remove V8's behavior of filtering the import assertions to only those expected by the embedder. The interop guarantees provided by doing the filtering in V8 are probably not worth the added complexity. Going forward, hosts will no longer need to provide a list of supported assertions, and they will be expected to ignore unknown assertions received from V8. The Blink code is already written such that unexpected assertions are ignored, so the only thing that needs to be done on this side is to remove the DCHECK that expects at most one assertion. Once the V8-side changes are made to remove the filtering, Blink can then stop setting v8::Isolate::CreateParams::supported_import_assertions. Change-Id: I40578c40ff4c97cd64b6bb0840b72163e9c5a2f1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2643059 Reviewed-by: Kouhei Ueno <kouhei@chromium.org> Commit-Queue: Dan Clark <daniec@microsoft.com> Cr-Commit-Position: refs/heads/master@{#846179}
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.