in reply to Re^4: More CSS-friendly formatting on PerlMonks? (no PRE)
in thread More CSS-friendly formatting on PerlMonks?

It is my impression that at least a few other browsers don't have this "problem". But I don't know much of anything about CSS and had almost nothing to do with the CSS on the site.

Would a SPAN work better? If Mozilla will only do it correctly with a block element, then it could be PRE in some cases and P in others. That seems like a pain, though.

                - tye
  • Comment on Re^5: More CSS-friendly formatting on PerlMonks? (no PRE)

Replies are listed 'Best First'.
Re^6: More CSS-friendly formatting on PerlMonks? (no PRE)
by Aristotle (Chancellor) on May 02, 2003 at 07:25 UTC
    The CSS box model seems weird at first, but it's consistent and makes sense. Browsers that "don't have have this 'problem'" are broken. <tt> is an inline element and must not render like block level ones. However, one can simply declare tt.code to be a block element by adding a display: block attribute, since CODE blocks without newlines in them are not given the class="code" attribute. If that ever happens one could still narrow the rule using pre tt.code or some such.

    Makeshifts last the longest.

[reply]

      Then maybe "display: block" is how people are doing blockish display of code blocks already. I just know I've seen several people do it. I didn't look how they did it. So it probably isn't that there are any "broken" browsers, just difference in what people are trying with CSS.

      For example, thepen uses this: 

      tt.code
{
    background-color: #FFFFCC;
    border: thin black solid;
    padding: 10px;
    color: black;
    display: block;
}

      [download]

                      - tye
[reply]
[d/l]
        Ah, now I see what you meant. That's what my own CSS does, too.

        Makeshifts last the longest.

[reply]

In Section Perl Monks Discussion