James Addison

> Yeah those are too controversial to roll in here. We intentionally don't have single-select elements issue `unselect` because that'd always be paired with a `select`. Sounds good; the single-select...

Also a note: the `jquery-mockjax` component is available under dual MIT-or-GPLv2 licensing terms (it's up to the authors of the codebase where it is included to decide on the applicable...

Hey @kevin-brown - I'm afraid I'm joining the chorus of 'any updates on this' here - is there anything I can do to help this and/or the 4.1.0 milestone along?

Note, partly since licensing was discussed here previously: `jquery-mockjax` v2.6.1 has consolidated from dual MIT-and-GPLv2 licensing to a single MIT license (ref: https://github.com/jakerella/jquery-mockjax/commit/8183c940d8b41faaaec39657c4e931273645eab9 and the [associated changelog entry](https://github.com/jakerella/jquery-mockjax/blob/4ca7ace3daf8cfb54134555ee91c4b1cff671065/CHANGELOG.md?plain=1#L2)).

Argh, I don't think this is testing the correct behaviour. Currently the code here tests clicks on the 'remove' button on each tag within the multi-select. Re-attempting the demo from...

Ok, the test coverage here for #3882 _seems_ to also validate the fix attempted originally in #6179 (subsequently reverted due to lack of test coverage). Even so: I don't think...

Yep, that sounds sensible - I'll take another look at the code and see how to refactor it like that.

(I guess that's not really refactoring; more like a better fix. anyway, taking a look into that now)

Having an automatically updated report to display scrapers health sounds great; it'd be useful for maintainers, users and contributors alike :+1: The green, yellow, red mapping sounds like it'd fit...

> Those are thus not repeatable or reliable and any exact string matching like this are brittle tests and are providing some false signals In many codebases, the tests can...