SSI kills CSS button

[Haines Brown]

I have a CSS button built up by using shaded borders. For the
button's label I wish to include a string returned by SSI
echo for HTTP_REFERRER. However, by adding the SSI include statement,
the button disintegrates, as if the nesting were being dispaced by the
SSI include statement. Here's the url:

http://www.hartford-naacp.org/agenda.shtml

--

Haines Brown
KB1GRM
ET1(SS) U.S.S. Irex SS-482

[Andy Dingley]

Haines Brown wrote:

I have a CSS button built up by using shaded borders. For the
button's label I wish to include a string returned by SSI
echo for HTTP_REFERRER.

OK

However, by adding the SSI include statement,
the button disintegrates,

Nope. SSI is ALWAYS transparent to the client. Just look at the static
HTML produced after the SSI has been processed. If that looks OK but
still has a problem, then it's clearly a CSS issue

http://www.hartford-naacp.org/agenda.shtml

Sadly I haven't got time to fully investigate this. But you've got <a>
nested inside <athere, which isn't valid and you've also got CSS
selectors based around <aand a descendant selector, not a child
selector. Those are certainly going to get awfully confused with
multiple nested <a>.

I'd start by removing that multiple <a>

This code works fine. Re-organise your SSI to produce this instead
(shouldn't be hard)

<div class="bttn">
<a
href="http://www.google.com/url?sa=D&amp;q=http://www.hartford-naacp.org/agenda.shtml">
<span class="a">
<span class="b">
<span class="c">Back</span>
</span>
</span>
</a>
</div>

As a totally separate issue, you're serving XHTML (dubious) and you're
serving XHTML 1.1 as Appendix C (simply wrong). You'd arguably be
better not using XHTML at all (this is up to you), but if you do want
to use XHTML this year, stick with XHTML 1.0 and Appendix C. This is
both valid, as useful as any XHTML, and it works with the browsers out
there.

ET1(SS) U.S.S. Irex SS-482

One of the very last Tench class, wasn't it? Just missed combat in WW2
?