I would definitely be in favour of a wider textarea to edit my posts. Having said that, is it actually the sidebar that's limiting the width?

I've long had this css (courtesy of some other kind monk who's name I've long since forgotten), in my Display settings/On-site CSS markup thingy:

textarea { width: 100%; height: 25em; }

That has the effect of doubling the width over the standard view, at which point it butts up against the sidebar. A very useful increase, but still less than it could be.

I still find it limiting when, as my old eyes get tired, I zoom the page to 150% or 200% to compensate. Trouble is of course, the sidebar also gets bigger. So as the font increases in size, the effective usable area barely changes or even starts to shrink.

Were I able to turn off the sidebar, not only would that increase the screen real-state available for use in the textarea. It would also avoid the annoyance of seeing a new /msg appear, instinctively click it, and watch what I've typed so far disappear in to the lottery that is the browser cache.

Most times you can back up to it, but sometimes--always when you've typed the most because you've been using lots of other tabs to do research--when you back up the page has been flushed from cache and Whoops! Sorry. All gone. Which is intensely annoying.

I also think that clicking or responding to /msgs is responsible for a lot of duplicates posts, so it might help there also.

But best of all, anything that reduces the impact on the PM servers has to be good right?


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP an inspiration; A true Folk's Guy

In reply to Re^2: Could we lose (or turn off)the sidebar during preview? by BrowserUk
in thread Could we lose (or turn off)the sidebar during preview? by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.