This isn't a problem I've observed. I think it's on your end
Changed the thread title from "A Year Later: STILL No Scroll Bars?" so that it isn't an angry rant.
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." - Richard Feynman
The Unknown
I'm confused as to what the issue is. The edit window has a scroll bar.
Are you talking about forum posts?
edited 8th Feb '16 12:29:58 AM by Karxrida
If a tree falls in the forest and nobody remembers it, who else will you have ice cream with?
I have this problem as well and it can be a little annoying on large pages. I would note though that this isn't the only site that it happens with as it is also an issue when I write reviews for Amazon so it may be a compatibility issue.
edited 8th Feb '16 12:54:01 PM by SebastianGray
@Septimus Heap *Sigh* This wasn't intended to be an angry rant in the first place; sorry it came off that way.
@ Karxrida It's all throughout the wiki irregardless if you're posting in a forum thread, replying to a YKTTW thread, editing a YKTTW draft, or anything.
I've seen it on forum posts and page edits.
Lost in Space
The scroll bars all work fine for me, so it's hard to say what the issue might be.
"It's Occam's Shuriken! If the answer is elusive, never rule out ninjas!"
Should probably be reposted in the noticeboards with much more precise information, so locking here.
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." - Richard Feynman
It's been about a year or so since the last major update to the wiki right? During this time, I've reported a bug/glitch that's come up as a result of the update: no scroll bars on text boxes. If you're typing/editing in a text box, the only way you can get from one point to another is to hold down the up or down arrow keys to get to where you need to type/edit. I see after all this time, there's still no scroll bars on text boxes. Has nobody looked into this? Is there no fix for this? I know I'm not too active here anymore, but it seems like during this time, this would have somehow been fixed by now.