They’re sensible suggestions. I think the problem with the “preview” page setup here is, it all depends on what kind of endpoint you’re using (portrait vs landscape, screen resolution, mobile or desktop, etc.)
Some WYSIWYG box for putting a post together would be nice - because if I’m writing a post on a phone, having one box with the HTML in it and another with the preview (with the page layout totally different to that of the thread display) is clunky.
Many’s the time I’ve looked at the “Your reply” box and it seems OK, I then preview it, it looks okay, I submit it, read it back, but it looks different to how it was presented in the preview... This is especially the case if I write a post on my phone, but later that day I return to read FR on my home computer - which has an ULTRAWIDE monitor.
The page width on the “reply” screen is set up as if I’m using a 1024x768 display from 2002, but the thread display uses the full screen width. So the “preview” is not actually that reliable for seeing how line breaks and word wrap will render differently.
For fun, put a thread view into https://pagespeed.web.dev/ (which will analyse it for readability and accessibility) - while it scores well on desktop viewing, it falls short on a number of criteria for mobile browsing.
I’ve had to stop using FR in the browser on my Android phone; it defaults to the desktop view which is totally unreadable, and I haven’t been able to figure out how to force it to render in the “reader” mode or a mobile-friendly mode instead.