System font variants such as monospaced don't work

[jcovin293]

In a RichText view with a Configuration with a fontType value of .monospaced or another value that is not .system, the website instead uses a serif font. Here is a code example:

RichText(html: "<h1>Hello World!</h1>", configuration: Configuration(
    fontType: .monospaced
))

This is similar to #49 where @RushanB describes the issue where custom fonts are not displaying as expected. This seems to be an issue with the CSS.

[NuPlay]

This was fixed in v3.0.0, and the last remaining part of it is fixed in #79.

Original symptom. FontType.name used to return the raw PostScript name - .AppleSystemUIFontMonospaced-Regular for .monospaced. A CSS family starting with . is not a valid unquoted identifier, so WebKit discarded the whole font-family declaration and fell back to its default serif face, which is exactly what you saw. v3.0.0 returns real CSS stacks (ui-monospace, 'SF Mono', Consolas, ...) and quotes custom names. There is now a test asserting font names never start with ..

What was still broken on 3.x. supportsDynamicType emits font: -apple-system-body, and the font shorthand resets font-family and font-style. Those rules are appended after the generated CSS, so turning on Dynamic Type silently discarded fontType again. #79 re-asserts the configured font after the Dynamic Type rules, with selectors specific enough to also cover p.subheadline, p.footnote, p.caption1 and p.caption2.

fontType and supportsDynamicType now work together. Please reopen if you still get a serif fallback.