Conversation
|
I would do most of these as cases within a feature directory, instead of calling each case its own feature. They are mostly of interest to developers so they could be shown under the (But all questions of feature granularity are subjective.) |
The question, I guess, hinges on whether the single document still allows tests and minimal examples without a clunky .qmd full of extraneous divs (for the selectors) |
|
Still separate qmd files, just in a directory. Like all these cases for CSS border, which we wouldn't want to expose to the end user in the ff matrix, but which are helpful to the developer: (Here I think I went too far, and some of the invalid/error cases belong in regular smoke tests.) |
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) |
Progress towards #9832.
Fixes
This fixes the inconsistent border radii for callout headers in HTML, from
to