Skip to content

Conversation

@anandaroop
Copy link
Member

@anandaroop anandaroop commented Dec 22, 2025

This PR resolves DIAM-246

Description

Some articles include H1s and unordered lists, which are not rendered correctly.

H1s would seem unconventional since they are presumably reserved for article titles, but some articles (example) do make use of them and they are handled appropriately on web. Header styles are adjusted here accordingly, to preserve the relative size relationships between article header and body.

Header H1
(in article body)
UL
&LI
Before header h1 ul
After haeder h1 ul
mWeb
(for comparison)
header hi ul

PR Checklist

  • I have tested my changes on the following platforms:
    • Android.
    • iOS.
  • I hid my changes behind a feature flag, or they don't need one.
  • I have included screenshots or videos at least on Android, or I have not changed the UI.
  • I have added tests, or my changes don't require any.
  • I added an app state migration, or my changes do not require one.
  • I have documented any follow-up work that this PR will require, or it does not require any.
  • I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

  • I would like at least one of the reviewers to run this PR on the simulator or device.
Changelog updates

Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Need help with something? Have a look at our docs, or get in touch with us.

Comment on lines +87 to +93
li: {
fontFamily: FONTS.regular,
color: color("mono100"),
marginBottom: "1em",

...variantStyles,
},
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Something is up with the disc alignment for these li's but I haven't figured it out yet.

Screenshot 2025-12-22 at 6 16 32 PM

Copy link
Member

@MrSltun MrSltun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you roop 🌟 🙏

Copy link
Contributor

@brainbicycle brainbicycle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks great thank you! I am wondering if there is any way to get ahead of these in the future, that is what usually seems to happen now is someone publishes an article with some elements the app doesn't support well, they see it in the app, file a bug and then we rush to fix it. Is there any way we could review articles for what the expected html spec support is? or codify what the expected support is? or offer previews on app before publishing? I don't necessarily think any of those are worth doing now, just thinking out loud if this keeps being a problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants