If you never run `content_shell --run-web-tests` from the command line, you can stop reading now.
tl;dr -- `content_shell --run-web-tests` will soon switch to using threaded compositing by default. Currently, the default behavior of `content_shell --run-web-tests` is to disable threaded compositing and threaded animations. As part of an effort to enable threaded compositing by default for (web|wpt)_tests, we will invert that behavior <https://chromium-review.googlesource.com/c/chromium/src/+/4736695>, i.e., the default behavior will be to run with threaded compositing and threaded animations. This will *not* change any behavior when using the test runner scripts ( run_web_tests.py <https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/tools/run_web_tests.py> and run_wpt_tests.py <https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/tools/run_wpt_tests.py>). Those scripts always explicitly specify their behavior by adding either `--enable-threaded-compositing` or `--disable-threaded-compositing --disable-threaded-animation` to the command line for content_shell. There is only a change in behavior if you run `content_shell --run-web-tests` without an explicit `--(en|dis)able_threaded-compositing` argument. Questions/comments/suggestions: yotha@ and/or szager@ -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHOQ7J-QQTj5pf0GSWQoJMespp7zMUxHneQ28hRbjR%3DhHRzV3g%40mail.gmail.com.
