This happens when the quote is placed at the very bottom and there's no new-lines under it (no paragraph tags after it in the equivalent html, to be more precise). Personally, more often than not I find the opposite occurs - you can't enter text above the quote without moving it down, as opposed to being unable to enter text below it without moving it up. The issues are essentially identical however thanks to the U(p)/D(own) position buttons.
You can technically still type under a quote when this happens by simply moving the quote up - adding an empty new line above the quote using the return key above the quote, hover over the quote and click the U button in the position section of the pop-up, this will move it up 1 paragraph section, which as you used return to add a newline, simply puts it above that new line, essentially moving the new line below the quote. This can also be used to add lines between 2 quotes as well of course.
Similarly, when unable to type above a quote you can add an extra line below it and then move the quote down, allowing text entry both above and below.
You should always be able to type either above or below a quote unless you delete all of the content above a quote after placing it and not being able to immediately add content under it - and provided you can do one, you can use the other simply by adding an extra new line then using the U/D position buttons for the quote to move it between lines/between gaps between paragraph tag pairs.
Easiest reproduction for being unable to post above/below quotes would be:
i) put in any random brief text and quote a random message.
ii) move the quote up
iii) delete the extra line at the bottom below the random text you entered previously.
iv) move the quote back down
v) delete the line above that had text in it using the delete key until it disappears/joins with the quote box.
You can no longer add message content above or below the quote as of part (v) being complete, and you can no longer add text under the quote without 1st moving the quote back up as of part (iv) being complete.
If part (v) is complete then the only way to correct it is the delete everything to trigger the automatic p tag addition when something is 1st added to the message.
Note that realistically this should never happen unless done intentionally, certainly not all the way to part (v) being complete, anyway. Part (iv) and prior can be reversed so long as part (v) is not complete as well:
a) after part (iv) above is complete, move the quote back up, reversing part (iv)
b) add an extra line at the bottom underneath the random text, reversing part (iii)
c) move the quote down, reversing part (ii)
d) You're left with text entered at the top, a quote, and the ability to enter text underneath - of course that can all be deleted to reduce it to a blank slate as well if desired.
Long story short: this occurs because paragraph tags sometimes only exist either above (or below) the quote - using the U/D position buttons after simply adding additional lines/paragraph tags is the easiest way to correct that on the spot.
Personally, I see this more as a lack of clarity than an actual bug, however one way to avoid this clarity issue occurring would be have quotes always add <p></p> immediately before and after the quote code when inserted (if they're not already present), to ensure that text can be added both above and below regardless of where it's inserted. The extra p tags needn't be attached to the quote beyond that, for instance when using the U/D position buttons it'd be fine if it still just moved the quote tags themselves, and the extra spaces should remain deletable in the same instances they currently are too. This way anyone preventing typing underneath quotes using the D button (or above using the U button) should be able to realise that it's simply because they've moved the quote to the extreme bottom(/top) of the post and using the U (or D) button once would correct that - provided they haven't deleted a bunch of lines/p tags, which in itself would hint at adding an extra line to fix it. That said, as previously mentioned, even without those extra paragraph tags it's already possible to always add an extra line yourself and using the position buttons on the quotes to make typing both above and below possible - the cause just isn't quite so clear.
PS@LarkAnderson: Any chance we can get colour options for text on the editor like on the old site in the future? As is I find a fake link is most effective way of making text stand out when ideal, which in itself appears to require the use of a mod/staff-only feature to actually get it to go through, and even then converts it into a proper link, merely to a default page("///" which ends up calling things like about:blank) when I'd obviously prefer it wasn't click-able at all.
Log in to comment