Shienvien

Mahz's Dev Journal

...Again, we don't really have multi-field forms over here. Tab did exactly nothing for me until now (didn't try with thread creation, maybe it does something when there is a title field and text field). As it is? It is basically useless unless it is tab character.

Er, and no - I don't ever use external documents for post creation, so it is not really an acceptable workaround.
Edit(for the sake of curiosity, I suppose): Copying over a snippet of code with tab characters in it from a plain text file seemed to work fine in preview, though; don't feel like hunting down a rich text editor for the express purpose of finding out whether the tab characters in would be preserved.

Oy, and plenty of browser-based text editors do accept tab characters. So it is not like tab characters are unheard of in browser environments... In forums? Yes, typically no tab there. Elsewhere? Some Wikis, all net-based code editors, many plain text and pre-format entry fields, et cetera, all those accept tab characters without a hitch.
More bizarrely, even plenty of HTML form text fields I've encountered accept tab characters just fine, they just get omitted once the text is rendered, excluding when it is interpreted as pre-rendered text. To think of, some forums let you enter tab characters, but later omit them, too...

Mahz's Dev Journal

The shift-tab key should produce the white-space character since the tab key is reserved by the browser and by operating systems for keyboard navigation to the next form component, and making the tab key produce the white-space character would obviously conflict with that.

Not on all systems... And we don't really have many multi-field forms here to begin with.
- All programs I've personally excessively used either use it as spacer or autocomplete (latter mostly only for commandline/terminal/console-based programs, though the the terminal also uses it as spacer in some very specific instances). ...Excluding computer games, where it is often minimap, console-call, or some such unless I've mapped it to some other commonly-used function, since it is conveniently right next to WASD (though I use QWSD instead).

The Prophecy

@cthulu: A small note - the shirt was from Aemoten, not the guards (all Aemoten's shirts are long enough to reach her mid-thigh, and both buttonless and sleeveless), and her boots would still be her own (her boots should still be in fairly decent condition as she didn't take the brunt of the goblin attack; she simply left them to dry yesterday since they were soaked after two days of downpour). Alaine only left her a skirt and pants. (The slightly too big boots were for Aemoten.)

It is also rather cold outside - it is autumn, after all.

(OoCly, Brand's raven is indeed a she, so Thaler was actually correct in that. She has a name, too - Beatrice -, but our characters never really heard Brand call her by her name in their vicinity...)

---

As a sidenote, we have can use the tab character now. I can finally make paragraphs the normal way, and don't have to fall back to dumb alternatives or some kind of arcane sorcery to make my paragraphs a bit more distinct without having to resort to double line breaks (the empty lines of which tend to disjoint the text to the point where I myself tend to have difficulties actually following the text when people use it for very short paragraphs or, say, dialogue).
On earlier days I've simply left my posts with single line break paragraphs, lately I've taken the effort to either fetch some of the lesser-known whitespace characters that aren't typically omitted on forums and in plain HTML (en space and em space and such are typically fairly sure way - in browser-HTML you just type in the codes for them, in most other places you don't need them since other whitespaces are respected but they exist regardless, on forums you basically have to paste them ... Win also has an alt-combination (Alt+2002), but as it is, I am typically not on Windows), or - speaking of dumb solutions - blank images, background-colored underscores... But now I finally have my tab character back (as well as multiple spaces).
Yes. Tab character working properly. On a forum. Strange things do happen...

Mahz's Dev Journal

Tabs doing what they are meant to do in browser? On a forum, of all things? Strange things do happen, strange things do happen indeed...
(If we're going to make tab/shift-tab distinction, then I'd rather tab was the whitespace character and shift-tab the whatever keyboard navigation thing Captain mentioned. If for no other reason, then for wanting more paragraphs than ... differently-styled text? I never noticed tab doing anything before besides, well, not working. - And I did try whether it did something with the new editor, just in case. Perhaps it is browser-specific.)
But thanks; it is certainly a thing I have direly missed for a long time, especially in a forum that is dedicated for creative writing.

Mahz's Dev Journal

Most browser-based environments lacking proper way to make longer rows of whotespace characters has always been a major annoyance of mine. I want my tabs, and I've resorted to colored underscores and worse to get them in the past... (Unless I jut give up and just use single line breals without tabs, which can be a bit textwallish.) - I really don't like double line break paragraph breaks (as opposed to your typical book-style single line break and tab). Not only do double line breaks result in questionable amounts of void, but I also find such text physically hard to follow when the paragraphs under question are very short.

Mahz's Dev Journal

@Mahz: The hugetext seems to have come (and gone?) with the force device width feature. The force device width option still exists on my profile, but it doesn't appear to do anything anymore; I see the desktop version either way now ("Desktop version" is not enabled from browser). The smalltext I first encountered on RPG earlier today, I think... I have seen it on other sites, however, so it is not entirely Guild-specific. Smalltext in posts seemingly only occurs with very short posts. Using Firefox (both latest 37 Beta and 35 stable release give the same result) and Android. Checking further... - Chrome 40 doesn't have smalltext bug. - The native browser (Samsung's? where is this thing's version info?) doesn't have smalltext, either, but holy white buttons...

Mahz's Dev Journal

@Mahz: What I had was different (and in my opinion, even more hindering*). I see the occasional smalltext now, too, though ... it even seems to affect the content of some posts, not only signatures. *The text - all text - was huge and couldn't be zoomed out any further with the force device width on. It was a bit annoying with the forum views, but posts were just terrible - margins 1/5 screen width on either side, text so big that it only fitted two to four words per row.

Mahz's Dev Journal

There, I supersized the tabs for you to better bring out the shadow effect I am talking of: (Browser zoom, not photo editor zoom.) And I just noticed the "None" text in Preview error check has similar shadow effect.

Mahz's Dev Journal

@Mahz: The RP tabs appear to have the same shadow effect as the white text on, for instance, Quote and Mention buttons. Since both the text and shadow are black, the text just turns slightly fuzzy, or smudged. I did stare at those a bit before I figured out what was off (and that my screen wasn't failing at delivering a clear text, somehow). Zooming in makes it more apparent now that I check; perhaps I should also fetch you a maximum-sized example.

Mahz's Dev Journal

If that's the case, are we going to revert the first/last page buttons into ovals?

LegendBegins

I'd support it - the current buttons are a bit unrefined, and on smaller screens, the borders tend to get (paritally) "eaten" (which leaves just floating links). And while we are at it, could the hover color be changed to something other than white? Edit: Another tiny styling thing: could the shadow effect on tabs be removed? It makes the text look fuzzy in forum view.