Latest Fixes October 9

Typos or Grammar

From the Dashboard page, under the You Have 1 New Subscribers heading:

"Clock the relevant Manage Subscriber..." S/B 'Click'.

Under the You Have Group Administration Tasks heading:

"Click on a group name to go to the relespective administration page" S/B 'respective' and need a period at end of sentence.

From the Update Your About Page page (/groups/My_Private_Fnora_Office/editAbout.fn):

"If your group rules,..." Missing word, 'has'...

Under the What your About Group Article Will Look Like heading:

"...use the inline buttons to upload missing images if any." Missing comma after 'images'?

On the Modify Group Permissions? page (/groups/My_Private_Fnora_Office/changeType.fn):

"...as well as for changing the the default permissions..." Repeated word.

In the Can Comment with Moderation. section:

"...viewed by a moderator before they appeal." S/B 'appear'.

On the Update Your Privacy Settings page:

"...sock pupputs,..." S/B 'puppets'.

On the Privacy Settings Update Successful! page:

"...can send you a private message currently" Missing period at end.

On the Short About Me Update Successful! page:

"Or just click the FNORA logo..." Reference to Fnora from a Conntects page, potentially confusing. I think I've seen multiple instances of these inconsistencies that should be reconciled.

That's all for now, I think you refer to these things as nitnoids. Just trying to help you polish this baby up to a high shine.

Fixing nitnoids is important! Thanks!

More Typos

On the Create a New Post page, in the Tags section:

"Mult-word tags..." S/B 'Multi-word'.

"You can have up to five tags per postj" S/B 'post.' Missing period.

In the And now the post proper. section:

"...you can hit the Post button..." You've relabeled the 'Post' button as 'Publish'.

FYI, I've lost a couple drafts toggling between browser tabs while composing a post...

###

Phooey! I thought I had the lost data problem fixed. It's supposed to give you a popup when you have unsaved data and you close a window.

Until I get it fixed, remember to hit Save Draft now and then. They My Stuff "tab" for the group or blog will list your drafts.

P.S. Have you tried the Edit in New Window button? In that mode you get line numbers -- at the price of no wrapping. (This can be useful when pasting from a word processor. Each paragraph is a line and it is easier to add the needed line breaks. One of these days I intend to automate that process.)

I think I have all the typos fixed now. Hopefully, I didn't introduce any new ones.

I tried to replicate your losing of drafts without success. When I try to leave a page with unsaved data, I get a popup. At least that's the case in Mozilla. Are you using a different browser?

I'll give Chrome and Brave a try in a bit.

OK, I can replicate your problem in Chrome.

To avoid losing data, use Mozilla until I can figure out how to prevent losing data in Chrome.

Thanks a lot, Carl. I resorted to the separate window editor after I lost my draft, and that worked fine. I'm using the Brave browser, which I understand is based on the Chromium source code.

OK, regarding the loss of unsaved data, I think I have it fixed.

For Mozilla, a call to preventDefault on the event caused a popup to allow the user to cancel out. For Chromium, I had to add a return value attribute to the event.

I'll check to see if this works on Chrome proper in a bit.

Tested with both blog and group posts using Chromium. Still to do for personal posts and About pages.

Not Done

It is still possible to leave a page with an unfinished comment. This is lower priority since comments are generally shorter than posts, but I'll put it on my todo list.

For big posts the separate window editor is handy for other reasons. If you get a QTML error, you can do a preview with line numbers. It's quite handy.

It's also a bit better for finding the paragraph breaks when you paste from a word processor -- which generally just turns paragraphs into lines without the empty line in between which I use for paragraph breaks.

I noticed yesterday while composing a post draft I could not get blank lines between paragraphs/blocks, no matter how many blank lines I entered , and using the p tag didn't force blank lines in either the preview or publish rendering.

Let me try.

How is this?

Need to have some content even in empty paragraphs. The non-breaking space entity works. (See QTML)

This is a bit of a hack. Another, probably more a canonical approach would be to use the .type tag to get vertical space. After all, typewriter mode is supposed to allow visual typesetting...

Done typing.

Works for me. Thank you.