bug: ordered lists being turned into unordered lists across keyman.com

[alex-larkin]

Hello,

I'm not sure if this is the right place to put this bug report, but I have noticed that on some different pages, ordered lists are being turned into unordered lists.

For example, the markdown for this page uses numbers, and when inspecting the live page it uses <ol>, but it still appears with bullets:

The documentation for this popular keyboard also makes use of numbered lists in the PHP file, but it also shows up with bullets. (When viewing the page inside the keyman app, it shows up correctly with numbers. Interesting note: The PHP page has no custom CSS).

Chrome browser:

Keyman app:

My own keyboard documentation also makes extensive use of embedded ordered lists, sometimes specifying what type of <li> to use, but here also everything shows up as bullet points. The indentation for embedded lists is also barely perceptible.

Chrome browser:

Keyman app:

(I understand that the Keyman app is likely drawing from the welcome.htm)

I have also noticed that tables are being drawn without borders in the documentation in both of the mentioned keyboards. My documentation does have CSS to specify how to display tables. It also has a custom <kbd> CSS class for differentiating characters as they appear on the screen from keys on the keyboard, but in the browser everything is drawn the same. But I don't know if I should make a separate issue for that.

I hope if the numbering and indentation issue is solved it will make the site more user-friendly.

Any ideas on how this can be improved?

Also, please let me know if you notice I've implemented CSS incorrectly in my documentation in any way.

Thanks so much!

[mcdurdin]

Agree that ol vs ul list styles are wrong. We do need to do a refresh on the css across the keyman sites. There is a challenge in maintaining consistency between the overall site look and feel vs the keyboard documentation, and it's something we want to look at more closely in the future.

[alex-larkin]

Ok. If this is going to take a while, are there any workarounds that you can think of that I can use in the meantime? Thanks! El dom, 9 de mar de 2025, 17:56, Marc Durdin ***@***.***> escribió:

…

Agree that ol vs ul list styles are wrong. We do need to do a refresh on the css across the keyman sites. There is a challenge in maintaining consistency between the overall site look and feel vs the keyboard documentation, and it's something we want to look at more closely in the future. — Reply to this email directly, view it on GitHub <#556 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATS3DUBDRLTIQ4QMKY36N432TTBJXAVCNFSM6AAAAABYO3HZPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBZGEYTKMRQGA> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: mcdurdin]*mcdurdin* left a comment (keymanapp/keyman.com#556) <#556 (comment)> Agree that ol vs ul list styles are wrong. We do need to do a refresh on the css across the keyman sites. There is a challenge in maintaining consistency between the overall site look and feel vs the keyboard documentation, and it's something we want to look at more closely in the future. — Reply to this email directly, view it on GitHub <#556 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATS3DUBDRLTIQ4QMKY36N432TTBJXAVCNFSM6AAAAABYO3HZPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBZGEYTKMRQGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mcdurdin]

The problem with workarounds is that they will probably need to be unwound if we make changes to the CSS of the site. Our usual recommendation is to avoid custom CSS in the published keyboard documentation (.php) targeting the help site, and use the provided styles. You can embed <style> elements as a workaround, but not really recommended.