@foolip Philip,

I presume you are one of the wpt maintainers.
Is the svg flag valid or deprecated?
<meta content="svg" name="flags">
I have declared the svg flag in 2 tests
and in 2 reference files so far:
web-platform-tests/wpt#20033
web-platform-tests/wpt#21450
svg is not in the list of valid flags
http://web-platform-tests.or

Hi,

When I run my tests using the neovim strategy, it opens a new terminal but auto focus on the buffer. Then I have to press <C-o> to not close the buffer and go back to my split pane.

Is there a way to have it open but not switch my focus to the newly opened pane automatically?

The default output doesn't have much contrast and is a bit hard to read for me. That's best illustrated with a screenshot:

Hello, and thank for this module.
I am wondering if consideration has been given to adding colour to the stack traces printed out upon failure of a test. For a test runner emphasizing colour, this seems like an obvious omission. I have patched in this functionality using pygments in my fork: psacawa/green@1922bc8 in an ad hoc fashion t

Integrate: https://github.com/click-contrib/click-completion

When there are errors in the config, such as an incorrect import, they are intercepted by the regular try catch and only the error message is logged.

Logging of only the error message is useful for our own errors, where the stack trace has no added value. For user errors, the stack trace has added value.

We should create a special error type for errors we throw in the startup of the test run

This looks to be something legacy which hasn't been updated in several releases. I've asked Charlie Poole/Rob Prouse if they can remove it from the choco site, as maintainers. We should also remove the packaging from the repo here.

https://www.chocolatey.org/packages/nunit-console-with-extensions

Consider the below test case, the language is Icelandic.

The test explorer shows this test case as

Notice that \u0081 is being added in between two characters as a