User blog comment:DaNASCAT/Technical Update: May 8, 2012/@comment-3441771-20120509033114/@comment-3441771-20120512073342

Sorry guys... forgot I posted this:

@Dopp:

I see. I know you said to me in the past that it was being worked on, but (trying not to step on toes) it seems to be more of an issue than I thought it would be. I did think a "font family" addition would be easy. But there seems to be more compatibility issues than I foresaw.

I actually don't want a preview mode in the Mini-editor. (Found out today that it's actually just a cut-down version of the Full-editor. *Trivia*) I don't want the preview in a JavaScript pop-up at least. This would be an annoyance to me more than the lack of a preview. I have the following suggestions:


 * 1) When/if adding a preview mode to the mini-editor please add it inside the .editarea css class. Since this would contain the mini-editor better. This isn't needed on the full-editor because you don't have the article/blog above the editor to look at.
 * 2) A "show changes" button would be nice too! :)

Oh and I think you're wrong Dopp: if this was just the incorrect font; then why would it remove code. (I might have to test the source mode version for the same occurrence.) How about an example I dislike intensely:

I'm a division box.  I'm another. There was a clear between me an my friend.

I'm going to add in another two div-s into the comment after saving it: Oh dear!  You lot may have fixed it!

You have! May a thousand Camels smile upon you!

@Rappy: The system really doesn't like those HTML tags! :P