Huge empty area between tools and textarea

[Nerukou]

Hello,

I implemented the editor, but every time I load the page it has a huge empty area between the toolbox and the textarea. This empty area persists no matter which code I use. Any ideas on how to get rid of it? I've attached a screenshot to show what I mean.

[mr_lundis]

Hello Nerukou and welcome to the WYMeditor forum!

It's kinda hard to tell what's gone wrong just by looking at that screenshot, however I'm guessing there's some kind of stylesheet conflict going on.

Do you have the same issues using the default theme?

Cheers

[Nerukou]

Ok, I updated the screenshot to better show the problem. And yes, I have the same problem with any theme I use. I have included the stylesheet I use for my site.

Code: Select all

body  {
    background: #5CB85C;
    margin: 0; /* it's good practice to zero the margin and padding of the body element to account for differing browser defaults */
    padding: 0;
    text-align: center; /* this centers the container in IE 5* browsers. The text is then set to the left aligned default in the #container selector */
    color: #000000;
    font-family: "Trebuchet MS", Arial, Helvetica, sans-serif;
    font-size: 100%;
  background-image: url(templates/images/background.jpg);
  background-repeat: repeat
}

a:link {
    color: #000;
}

a:visited {
    color: #000;
}

/* Tips for Elastic layouts
1. Since the elastic layouts overall sizing is based on the user's default fonts size, they are more unpredictable. Used correctly, they are also more accessible for those that need larger fonts size since the line length remains proportionate.
2. Sizing of divs in this layout are based on the 100% font size in the body element. If you decrease the text size overall by using a font-size: 80% on the body element or the #container, remember that the entire layout will downsize proportionately. You may want to increase the widths of the various divs to compensate for this.
3. If font sizing is changed in differing amounts on each div instead of on the overall design (ie: #sidebar1 is given a 70% font size and #mainContent is given an 85% font size), this will proportionately change each of the divs overall size. You may want to adjust based on your final font sizing.
*/
.twoColElsRtHdr #container {
    width: 58em;  /* this width will create a container that will fit in an 800px browser window if text is left at browser default font sizes */
    background: #466d2a;
    margin: 0 auto; /* the auto margins (in conjunction with a width) center the page */
    border: 1px solid #000000;
    text-align: left; /* this overrides the text-align: center on the body element. */
}
.twoColElsRtHdr #header {
    padding: 0 10px;  /* this padding matches the left alignment of the elements in the divs that appear beneath it. If an image is used in the #header instead of text, you may want to remove the padding. */
    background-color: #408040;
    background-image: url(templates/images/header.png);
    background-repeat: repeat-x;
}
.twoColElsRtHdr #header h1 {
    margin: 0; /* zeroing the margin of the last element in the #header div will avoid margin collapse - an unexplainable space between divs. If the div has a border around it, this is not necessary as that also avoids the margin collapse */
    padding: 10px 0; /* using padding instead of margin will allow you to keep the element away from the edges of the div */
    color: #FFFFFF
}

/* Tips for sidebar1:
1. Be aware that if you set a font-size value on this div, the overall width of the div will be adjusted accordingly.
2. Since we are working in ems, it's best not to use padding on the sidebar itself. It will be added to the width for standards compliant browsers creating an unknown actual width.
3. Space between the side of the div and the elements within it can be created by placing a left and right margin on those elements as seen in the ".twoColElsRtHdr #sidebar1 p" rule.
*/
.twoColElsRtHdr #sidebar1 {
    float: right;
    width: 12em; /* since this element is floated, a width must be given */
    background: #77642a; /* the background color will be displayed for the length of the content in the column, but no further */
    padding: 15px 0; /* top and bottom padding create visual space within this div */
    border-top-width: 1px;
    border-right-width: 1px;
    border-bottom-width: 1px;
    border-left-width: 1px;
    border-top-style: solid;
    border-right-style: none;
    border-bottom-style: solid;
    border-left-style: solid;
    border-top-color: #40491e;
    border-right-color: #40491e;
    border-bottom-color: #40491e;
    border-left-color: #40491e;
}

.twoColElsRtHdr #sidebar1 a:link {
    color: #40491e;
}

.twoColElsRtHdr #sidebar1 a:visited {
    color: #40491e;
}

.twoColElsRtHdr #sidebar1 h3, .twoColElsRtHdr #sidebar1 p {
    margin-left: 10px; /* the left and right margin should be given to every element that will be placed in the side columns */
    margin-right: 10px;
}

/* Tips for mainContent:
1. If you give this #mainContent div a font-size value different than the #sidebar1 div, the margins of the #mainContent div will be based on its font-size and the width of the #sidebar1 div will be based on its font-size. You may wish to adjust the values of these divs.
2. The space between the mainContent and sidebar1 is created with the left margin on the mainContent div.  No matter how much content the sidebar1 div contains, the column space will remain. You can remove this left margin if you want the #mainContent div's text to fill the #sidebar1 space when the content in #sidebar1 ends.
3. To avoid float drop, you may need to test to determine the approximate maximum image/element size since this layout is based on the user's font sizing combined with the values you set. However, if the user has their browser font size set lower than normal, less space will be available in the #mainContent div than you may see on testing.
4. In the Internet Explorer Conditional Comment below, the zoom property is used to give the mainContent "hasLayout." This avoids several IE-specific bugs that may occur.
*/
.twoColElsRtHdr #mainContent {
    margin: 0 13em 0 10px; /* the left margin will look best if you match the padding amount to the header and footer. */
}
.twoColElsRtHdr #footer {
    padding: 0 10px;
    background-color: #408040;
    background-image: url(templates/images/footer.png);
    text-align: center;
  font-size: x-small
}
.twoColElsRtHdr #footer p {
    margin: 0; /* zeroing the margins of the first element in the footer will avoid the possibility of margin collapse - a space between divs */
    padding: 10px 0; /* padding on this element will create space, just as the the margin would have, without the margin collapse issue */
}

/* Miscellaneous classes for reuse */
.fltrt { /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
    float: right;
    margin-left: 8px;
}
.fltlft { /* this class can be used to float an element left in your page */
    float: left;
    margin-right: 8px;
}
.clearfloat { /* this class should be placed on a div or break element and should be the final element before the close of a container that should fully contain a float */
    clear:both;
    height:0;
    font-size: 1px;
    line-height: 0px;
}
-->

[mr_lundis]

Using the styles you provided I still can't reproduce this. There must be something else on your site that causes this issue, do you think that you could set up a test page?

If that's not possible, try stripping down the page to its bare bones (i.e. just the editor) then put back the original stuff, one thing at the time, until you can locate what's causing this.

Cheers!

[Nerukou]

You can find a copy of the page here.

[mr_lundis]

Okay, I've finally found the problem; the float on your sidebar breaks the whole WYMeditor skin. However there's a simple fix, just add the following CSS rule and you'll be fine.

Code: Select all

.wym_box { overflow: hidden; }

Cheers

[Nerukou]

Sweet.

Thanks for all the help, man. I was scratching my head. Not such an expert with CSS, I am.