Firefox 2, or: How I Learned to Start Worrying and Hate Rich Text
- Returns sometimes inserts BR, and sometimes inserts P, there’s no reliable way to tell which is going to happen, and they sometimes look the same based on nearby formatting;
- If the last word in the previous line is italic, and you switch to italic, and then type a letter, the letter gets appended to the previous line;
- In circumstances I haven’t entirely been able to sort out, the point is sometimes only half drawn, and either flickers between its upper and lower portions or only draws the top half; and my favorite,
- Sometimes the point on screen has absolutely nothing to do with where text is actually going to get inserted, appearing randomly in the text, over a random part of the page that may be entirely outside the editor, or even just not at all
Combine all of these misfeatures, and you make it painfully difficult to write blog posts that actually show up on the main page the same way they show up in my browser. It’s common for an article to look just fine in the composer, but to show up on the website thoroughly borked. Yes, I should be checking WordPress’ preview more carefully, but I also shouldn’t have to deal with this problem in the first place. I’ve reverted to composing everything in TextMate in Markdown and then just pasting the raw HTML. There is no reason that things need to be this way; every single platform that runs Firefox has built-in rich text components, and it’s not that hard to convert from RTF to HTML. All Firefox has to do is bow down, use native widgets, and then convert on form upload.
Oh well. Maybe someday.
Want to comment on this post? Join the discussion! Email my public inbox.