21d 15:22:31 until the OGMW forums will transition to fully read-only mode. Read more here.
For consistency with the new site, OGMW now accepts email address as a login credential in addition to user name. User name will eventually be removed, so we recommend getting in the habit of using email address going forward.
Additional troubleshooting. Looks like if the comma-space sequence pushes the closing fieldset tag to a new line in the editor window, a hard newline is inserted. Doesn't matter which forum.
test test test test test test test test test test test test test test test test test test test test test test test test test test te test,
a
Same behavior observed with a bold tag. Looks like if the closing tag is present (and valid to parse), pushing that closing tag off to the next line with a comma-space sequence causes the hard newline.
test test test test test test test test test test test test test test test test test test test test test test test test test test test test.
a
This time, I tried with a period-space sequence, and got the behavior again. It seems the punctuation may not matter as much as the space before the closing tag.
Punctuation-space sequence required. If the punctuation pushes the fieldset tag to the next line, the newline is inserted when the space character is typed. It appears to trigger on whatever script or browser functionality separates the preceding punctuation from the left bracket [ at the start of the tag.
test test test test test test test test test test test test test test test test test test test test test test test test test test test test ,
ab[/b]
OK, so it doesn't need to be a valid parsing sequence either. When the punctuation-left bracket sequence breaks across a line in the editor, adding a space character causes a newline.