Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Tue, Mar 29, 2016 04:56 PM UTC:
> So I fixed that and closed the ARTICLE and MAIN tags just before your wizard.

OK, I see what you are doing: you just put an unbalanced closing tag for MAIN and ARTICLE in the submitted text, and this will locate part of that text (in this case the Design Wizard, which initially is hidden) behind those elements. The fact that the display script still adds another {/MAIN} and {/ARTICLE} behind the Wizard does not matter; these are simply ignored by the browser.

With the screen width I have (enough for adding the left ad side bar), this makes the "fineprint" end up partly behind the article text, and mostly in the left side bar below the ad, however. This is a bit ugly.

I did find a work-around for that, which is structuring the submitted text as: 

{DIV class="middle"}
{ASIDE class="leftcol"}ad image{/ASIDE}
{ASIDE class="leftcol"}ad image{/ASIDE}
{MAIN}
{ARTICLE}
------------------------------------------
Normal article text
{/ARTICLE}
{/MAIN}
{/DIV}

{div style="display:none"}
Design Wizard
{/div}

{DIV class="middle"}
{MAIN}
{ARTICLE}
-------------------------------------------
{p}{hr}{div class="fineprint"}This 'user-submitted' page...{/div}
{/ARTICLE}
{/MAIN}
{/DIV}
where the part between the dashed lines is the submitted one, and that outside it what the retrieval script adds. On Firefox this has the desired effect: when the Wizard is hidden the fineprint displays normally below the article, with the same left margin, like it was in the same ARTICLE element. All tags are now balanced (after the retrieval script does it work, not in the submitted text).

Only caveat is that it is against HTML regulations to have multiple MAIN and ARTICLE elements.


Edit Form
Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

Top level header: <H1>

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: <H2>

  • Unordered list item
  • Second unordered list item
  • New unordered list
    • Nested list item

Third Level header <H3>

  1. An ordered list item.
  2. A second ordered list item with the same number.
  3. A third ordered list item.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

Alt text for a graphic image

A definition list
A list of terms, each with one or more definitions following it.
An HTML construct using the tags <DL>, <DT> and <DD>.
A term
Its definition after a colon.
A second definition.
A third definition.
Another term following a blank line
The definition of that term.