MF2 spec styles could be improved
Description
Activity
Mark Davis January 19, 2025 at 10:04 PM
It might have just needed a browser refresh
Eemeli Aro January 19, 2025 at 7:00 PM
I think the link in the description came from my browser’s autocomplete, but the issue was present on the ‘latest published’ and ‘46.1' versions that Steven posted links to. As he and I discussed on Slack, this seems to be an issue with the build that wasn’t/isn’t including the tr35.css file.
Mark Davis January 18, 2025 at 10:44 PM
I just checked the blog post, and it looks like it has the right links. Eemeli, where did that link in “used for its published version do not account” come from?
BTW, we had noticed a flaw in #9, that the text does not say at the top that it has “Final Candidate“ status. We’ll be fixing that.
Steven R. Loomis January 15, 2025 at 3:21 PM
the ‘published version’ link isn’t correct, can you try:
('latest draft')
('latest published')
('46.1')
Eemeli Aro January 15, 2025 at 9:33 AM
Could this be due to requests for https://unicode.org/reports/tr35/tr35.css returning a 403 Forbidden HTTP status?
Details
Details
Priority
assessAssignee
Reporter
Eemeli Aro
The MF2 spec source is currently written in Markdown, and its editor’s version is rendered on GitHub. The styles used for its published version do not account for all GitHub-specific syntax.
In particular, the non-normative
> [!NOTE]blocks are not sufficiently distinguished from other, normative text.