Re: Different padding different browser

On Wed, 5 Jan 2005 12:42:58 -0500, Harlan Messinger
<h.messinger (AT) comcast (DOT) net> wrote:

"Mel" <mel.m.heravi (AT) hp (DOT) com> wrote in message
news:41dc1911$1 (AT) usenet01 (DOT) boi.hp.com...

[snip]

div style=padding:10px>hello</div

[snip]

Use quotes to delimit attribute values, and you won't have this problem.

That was my first impression, too. However, attribute values don't need to
be quoted if they only contain letters, digits, hyphens, periods,
underscores and colons. As the one in question does, it *should* be OK.
I'd have thought that the problem is more likely to be different
margin/padding combinations across all of the elements involved.

Mike

--
Michael Winter
Replace ".invalid" with ".uk" to reply by e-mail.

Michael Winter <M.Winter (AT) blueyonder (DOT) co.invalid> wrote:

Harlan Messinger <h.messinger (AT) comcast (DOT) net> wrote:

Use quotes to delimit attribute values, and you won't have this
problem.

That was my first impression, too. However, attribute values don't
need to be quoted if they only contain letters, digits, hyphens,
periods, underscores and colons. As the one in question does, it
*should* be OK.

Not agreeing nor disagreeing, yet quoting attributes is still a very
good habit to develop. Might not actually fix this problem, but it's
certainly a good suggestion.

"Michael Winter" <M.Winter (AT) blueyonder (DOT) co.invalid> wrote

On Wed, 5 Jan 2005 12:42:58 -0500, Harlan Messinger
h.messinger (AT) comcast (DOT) net> wrote:

"Mel" <mel.m.heravi (AT) hp (DOT) com> wrote in message
news:41dc1911$1 (AT) usenet01 (DOT) boi.hp.com...

[snip]

div style=padding:10px>hello</div

[snip]

Use quotes to delimit attribute values, and you won't have this problem.

That was my first impression, too. However, attribute values don't need to
be quoted if they only contain letters, digits, hyphens, periods,
underscores and colons. As the one in question does, it *should* be OK.

My mistake. But, to digress, the line in the spec that follows the one you
paraphrase above says, "We recommend using quotation marks even when it is
possible to eliminate them." The reason for this is ease of reading and
maintenance, and here was a case where that came into play, because as the
code appeared on my screen, I thought there was a space after the colon. If
the value were quoted, I wouldn't have looked twice because the space
wouldn't have mattered even if it were there.

Just out of curiosity, though: what if you *tried* it to see if it fixed the
problem? It may be a browser bug.

I'd have thought that the problem is more likely to be different
margin/padding combinations across all of the elements involved.