unaccounted for spaces

Jan Roland Eriksson <jrexon (AT) newsguy (DOT) com> wrote:

You need to learn some decent terminology. Markup is about _elements_
while _elements_ are marked up as to where they start and end by the
use of "tags". Is that so difficult to grasp?

It also seems difficult to grasp that it obviously IS something that
most authors don't get.

Patience is a virtue. To a person for whom this is the first time
they've been exposed to this fact (likely) the above comes off as
haughty and superior. A great way to ensure the result we generally
see in exchanges in this ng....

On Tue, 11 Jan 2005 13:00:04 +0000, Steve Pugh <steve (AT) pugh (DOT) net> wrote:

Jan Roland Eriksson <jrexon (AT) newsguy (DOT) com> wrote:
...you did have one single '<p />' tag in the source as I got it
here (source obtained through FF)
I don't understand why the W3 validator did not catch that one.

Because <p /> is valid XHTML.

Ah, yes you are right.
That's one of many reasons for me to stay out of XHTML :-)

--
Rex

Jan Roland Eriksson wrote:

On 11 Jan 2005 02:39:02 -0800, "TerraFrost" <terrafrost (AT) gmail (DOT) com
wrote:

snip

Because of your BR elements and a series of "misplaced" white space
characters.

that was the problem, and i've since gotten the desired effect. thanks

Ali Babba wrote:

TerraFrost wrote:

snip

you write:
height; 2px

i guess you ment:
height: 2px;
that fixed the discrepancy in IE's rendering vs. Firefox's - thanks!