Basil Crow

> Combinations of these should be checked Quite a vague statement Daniel. But this is better than nothing I suppose. @frankie139506 Could you select a reasonable subset of the power...

@frankie139506 That isn't a sufficient set of test scenarios to mitigate our concern about possible regressions here. Daniel listed 4 axes of possible inputs to this code. To fully test...

This pull request is off to a promising start but requires additional effort to reach completion: effort that appears to have been abandoned. Since this pull request has remained incomplete...

> If it remains inactive for several weeks, I will label it as `proposed-for-close` in order to maintain an orderly PR queue and close the PR approximately one week after...

The gray background intended for the default theme applies even when I choose the Dark Theme, which makes Jenkins unusable in the Dark Theme.

Thanks Jan, sorry I missed that - I searched this page for "dark" but didn't search the dark theme plugin's open pull requests.

Causes [JENKINS-69370](https://issues.jenkins.io/browse/JENKINS-69370) (CC @janfaracik). This regression affects the connection of inbound agents. In the absence of a verified fix by the end of the week, I plan to revert this...

What are the next steps for this PR? As far as I can tell https://github.com/jenkinsci/antisamy-markup-formatter-plugin/pull/91 needs to be merged and released, then this PR needs to be updated to a...

With a passing test suite, this is looking close to ready (if not fully ready) from my perspective. Do others feel that the `mode` compatibility path is sufficient, or do...

`antisamy-markup-formatter-plugin` is fully covered by the compatibility path, so while that PR is valuable as a code cleanup, there is no need to hold this PR for that one. Whether...