Header 1 is TOO big for most cases.

@design_RG Headers 1 to 6 are all implemented with header 1 being 150% font size and each header drops by 5% with header 6 at 125%. They also have a gradient of bolding added on top of that.

@freemo Thank you.

Here’s how the post above renders on Pinafore. And on Mastodon web.

@design_RG don’t let it fool you that the dark theme is partially rendering the markdown.. that’s only because of how i’m implementing the style fix (its a path until next release so i don’t need to redo the whole server).. but i will address getting this working on the dark themes now.

@freemo I think the Pinafore rendering is spot on. 5% decrease on Heading size as you go down is too little, too small a difference to note.

And Heading 1 is show as huge, which is correct (and not recommended for Toots, as it annoys people )

Been there, done that and learned – Header 2 works well for titles of posts.

• H1 works well for my Blog page titles.
• H2 for all subtitles from that point on.

Nice looking text results.

@design_RG yea 5% is too little but i spent a lot of time tweaking it and different numbers have other issues.. for example if i do a 10% difference then that means h1 would be even larger.. if i start h6 at 110% then h1 would be 160%. Problem is if you start h6 much below 125% it doesnt look like a header it just looks like text. If you start at that point then h1 would be even larger.

What i did was i figured the largest text that is acceptable or even usable is 150% which i set for h1 (as you pointed out even that is a bit too large usually so its clearly on the upper end).. then I picked a percentage for h6 at the smallest useful end of the range (which seemed to be 125%) then just divided it by the headers inbetween.

@freemo I think you can use the smallest heading sizes as not really large text.

They might work as smaller text sizes than normal – for the Fine Print when wanted, like legalese and insurance forms, lol…

H6 is not used much at all, by the time you get to H3 it’s so close to normal text size that there’s not much use for it.

I would assume H4 to H6 might all be subsized compared to normal text size.

Nice news that the Pleroma project is alive and well.

@design_RG yea thats fair, you could do that. I wouldnt be opposed to making those changes either. Let me get it working in dark theme first though.

@freemo yes, certainly, no rush – and thank you.

I found a nice example of Heading sizes, all the way to 6. Take a look.

https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_headers

And the second screenshot is from https://www.yourhtmlsource.com/text/headingfontsize.html

@design_RG This is odd. I just switched to a dark theme to fix the dark theme issue you mentioned but turns out all the markdown is rendering just fine for me in dark theme.

Which theme, exactly, are you on that wont render for you?

@freemo I am using the Mastodon Default Theme, Full Width (Dark)

In Firefox (Waterfox).

@design_RG That is very strange indeed, I am using that theme and it seems to work just fine for me.

• Bullet points work
• As does quoting
• and everything else

hmm…

See, quotes work just fine

This all should work for me (or did a moment ago) in dark theme you mentioned.

@design_RG yea rendered just fine for me on the dark theme…

@freemo Just checked and…

It renders fine in MS Edge Chromium. So I suspected it could be a FF issue…

But then, it renders fine in a Private Window in FF, just shows the default white theme. Identical to Edge actually.

FF Screenshot, Priv Mode attached.

@freemo So it’s something in the Dark Theme, specifically, I think.

I am not even using the Collapsed Mastodon add on or any other extension which could be changing it.

@design_RG Very strange.. ill have to install firefox here to see if i can replicate it.

@freemo And I logged into MS Edge to see how it would render with the Dark Theme associated with my account.

It looks identical to the FF screenshot. But don’t spend much time with this, it might be a minor, niche problem.