I too experience this problem (in all browsers). My guess is that we both followed the advice for a larger textarea as you describe above.

After some experimentation, I made the following changes to fix the problem:

textarea {
    width: 75%;
    height: 25em;
}
[download]

And through some quirk of fate, I added a lengthy url to my Personal Nodelet that forces the nodelet bar to be wider than normal.

Now I enjoy the Monastery without the annoying horizontal scroll bar you mention above, my chatterbox is a nice width for reading, and I still have a sufficiently large textarea for comfortable use.

You're the winner! Changing my textarea to 75% worked! I no longer have ultra wide front pages.

Thanks for all the great suggestions everyone.

dmm

Procrastinate NOW! Don't put it off... --Ellen Denegerous

Setting TextArea.width to 95% is even better, since it is closer to my original intent, but the effect upon the front page that I was experiencing is still gone.

Thanks again for the tip.

dmm

Procrastinate NOW! Don't put it off... --Ellen Denegerous

You're probably seeing what you see because of your Code-Wrapping settings.

If you aren't using "Auto Code Wrapping" and if "Code Wrap Length" is large (or blank so you get the default of 70) then the width of the main body of the monastery gates is determined by how how long the lines of code are in nodes currently on the front page.

Even if you are using "Auto Code Wrapping" then he browser is making the call on which soft-hyphen to wrap at, so your results may vary.

If you uncheck "Auto Code Wrapping" and set "Code Wrap Length" to something small (like 40) you'll find that the Gates are very slim indeed.

If you aren't using "Auto Code Wrapping" and if "Code Wrap Length" is large (or blank so you get the default of 70) then the width of the main body of the monastery gates is determined by how how long the lines of code are in nodes currently on the front page.

What you say here is incorrect. Based on your later statements, I think you meant to s/aren't/are/ and are just a little inaccurate on the last part (it isn't the length of lines but the length of unbroken runs of non-whitespace characters, roughly).

The most common reasons for pages rendering too wide are:

1. Someone put a long line inside of a <pre> tag. This will affect everyone. /msg the author or solicit one of the janitors to fix the problem, usually by replacing the <pre> tags with <code> tags.
2. Someone put a really long string containing no whitespace in their node. This will affect everyone, though some browsers wrap on certain non-whitespace characters (and one browser, IE, is crazy enough to not wrap on certain types of whitespace such as spaces followed by slashes). Similar procedure for requesting a fix, which would probably be putting the really long string into <code> tags with a newline.
3. The viewing monk has "Auto Code Wrap" turned on, some code in a node contains a long string that contains no whitespace, and the viewing monk is either using a browser that doesn't support soft hyphen or has "Code Wrap Length" set fairly high. The most common reason used to be that the browser doesn't support soft hyphen (for quite a while, only IE supported soft hyphen, but now many of the newest browser releases support it).

   This will only affect the monk who has their settings misconfigured. If you see a very wide node and report it in the chatterbox and others don't see the problem, then you should check for this problem and probably turn off "Auto Code Wrap" (or upgrade your browser or set your code wrap width to something likely between 20 and 40).

4. The viewing monk simply has code wrapping disabled (and a node contains code that contains long lines). Like the previous item, this will only affect the monk with these settings so check yours (and turn code wrapping back on).

Clean this up and it might make a nice "faqlet" (site documentation node) on "Why does the page render so wide?" (or whatever).

- tye        

Firefox 1.0.4 still doesn't support &#173 aka &shy; (which PM uses), but it does support &#8203 and <wbr>.
So, this means Auto Code Wrap is currently broken in Firefox.

Nope, sorry. This was happening long before there was such a thing as code wrapping, I just never took the time to figure it out or post a query about it before. Thanks anyway.

dmm

Procrastinate NOW! Don't put it off... --Ellen Denegerous

FP looks ok to me. It may just have been a node that was too wide being misdisplayed. To find CSS related nodes do a Super Search for "site css", or just 'css' but restrict to 'PMD' and 'CODE'/Snippets or do a "site CSS lsdfgjldkfghkldfj" normal search.

Thanks, but it wasn't "a node", it happened all the time, apprently regardless of what was on the front page.

dmm

Procrastinate NOW! Don't put it off... --Ellen Denegerous

On main pages such as The Gates, there are no class or ID definitions in the table tags so I can't figure out how to narrow the "reply to" column.

Lines that don't wrap, will continue on past the margins and won't be completely visible.

Jon

/***  Force all tables to use hard dimensions.
      Exceptions will have to be handled 
      individually due to lack of class
      and id declarations on certain tables.  ***/

      table {
         table-layout: fixed;
      }

/***  For some reason the monkbar is too long.
      This may need to change depending on your
      setup.  ***/

      table#monkbar {
         width: 85%;
      }

/***  The section links were cut off.  ***/

      td.titlechooser {
        width: 40%;
      }

/***  My prefered width for the main area.  ***/

      td.main_content {
        width: 85%;
      }

/***  Big text editing box for replies.   ***/

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

/***  When viewing a node with replies, the
      replies table needs to be set back to
      auto   ***/

      table#replies_table {
        table-layout: auto;
      )
[download]