Relevant spec sections:

https://drafts.csswg.org/selectors-4/#the-dir-pseudo
https://html.spec.whatwg.org/multipage/semantics-other.html#selector-ltr

The interesting cases to test are from the definition of "directionality" in HTML:
https://html.spec.whatwg.org/multipage/dom.html#the-directionality

• element with dir="ltr" matches :dir(ltr)
• root element without dir attr

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

From https://polymer.slack.com/archives/CE6D9DN05/p1601887288223100

I have the following config

threshold: {
  statements: 95,
  branches: 59,
  functions: 90,
  lines: 95
}

And locally it gives me this

Code coverage: 85.58 %
View full coverage report at coverage/lcov-report/index.html

But in CI it’s different and I have no idea what fails

Code coverag

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

As of 3.17.0 there's a dependency on Microsoft.DotNet.InternalAbstractions package in .nuspec but it's unclear how it is useful - I cannot find any code in this codebase which would depend on Microsoft.DotNet.InternalAbstractions.

The problem is Microsoft.DotNet.InternalAbstractions is published in Nuget https://www.nuget.org/packages/Microsoft.DotNet.InternalAbstractions/ without mentioning an