From: Steve on
I have a div with two - three paragrahs in it. Each paragraph has
its own inline style tag with its own font size setting. When I set
the last paragraph's font size the font sizes for ALL of the
paragraphs change.

Why?

How can I stop it?

I.E>

<div>
<P style = "font-size:18px;">
blah blah blah....
</P>

<P style = "font-size:12px;">
yada yada yada......
</P>

<P style = "font-size:8px;">
yak yak yak...
</P>

</div>
From: VK on
On Apr 13, 12:50 am, Steve <tinker...(a)gmail.com> wrote:
> I have a div with two - three paragrahs in it. Each paragraph has
> its own inline style tag with its own font size setting. When I set
> the last paragraph's font size the font sizes for ALL of the
> paragraphs change.
>
> Why?
>
> How can I stop it?
>
> I.E>
>
> <div>
> <P style = "font-size:18px;">
> blah blah blah....
> </P>
>
> <P style = "font-size:12px;">
> yada yada yada......
> </P>
>
> <P style = "font-size:8px;">
> yak yak yak...
> </P>
>
> </div>

What browser are you testing on? It works as expected (decreasing font
sizes) for Firefox, IE, Opera and Safari

Either you current browser is badly broken, or inline styles are
overridden by some higher priority rule - which is not shown in your
sample.
From: Bergamot on
Steve wrote:
>
> <P style = "font-size:18px;">

Please read the group archives about *not* setting font sizes in px
units. The subject has been discussed ad nauseam. See also
http://k75s.home.att.net/fontsize.html

--
Berg
From: Eric B. Bednarz on
Steve <tinker123(a)gmail.com> writes:

> I have a div with two - three paragrahs in it.

No, you have a problem that you do not understand, and nobody will be
able to properly explain it to you until you reveal it in context (the
latter being a resource served from a http server).


Here's a general debugging hint: if you were able to identify
problematic areas in your code, you would know the solution already.


--
||| hexadecimal EBB
o-o decimal 3771
--oOo--( )--oOo-- octal 7273
205 goodbye binary 111010111011
From: dorayme on
In article <m2wsn25z4w.fsf(a)nntp.bednarz.nl>,
Eric B. Bednarz <bednarz(a)fahr-zur-hoelle.org> wrote:

> Here's a general debugging hint: if you were able to identify
> problematic areas in your code, you would know the solution already.

Sounds good and if you pick your cases well it covers good. But in
general, it is not true.

--
dorayme