Re: HEX EEEEEE COLORS WITH IE

They are the very definition of HTML. You can follow them or not. If you
follow them, your pages will validate and you will be happy and prosperous.
If you don't follow them, your teeth will get long, and you will be an ugly
person.

The community and the manufacturers have embraced them as the "standards".
Call it what you will.

--
Murray
--------------
MVP FrontPage


"Thomas A. Rowe" <tarowe@xxxxxxxx> wrote in message
news:OnG9QUzXHHA.3952@xxxxxxxxxxxxxxxxxxxxxxx
From Merriam-Webster Online:

recommendation:

1a: the act of recommending
1b: something (as a procedure) recommended

The W3C states they provide recommendations. So far nowhere have I seen
them state that they are issuing "standards".
--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

http://www.Ecom-Data.com
==============================================


"Murray" <forums@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uB6e4NzXHHA.2552@xxxxxxxxxxxxxxxxxxxxxxx
The recommendations are the standard.

--
Murray
--------------
MVP FrontPage


"Thomas A. Rowe" <tarowe@xxxxxxxx> wrote in message
news:u303y9yXHHA.2436@xxxxxxxxxxxxxxxxxxxxxxx
That is one way of looking at it, but that still doesn't make them
standards.

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

http://www.Ecom-Data.com
==============================================


"Kevin Spencer" <unclechutney@xxxxxxxxxxxx> wrote in message
news:uQNK3uyXHHA.1216@xxxxxxxxxxxxxxxxxxxxxxx
Well, Tom, it seems that all of the browser vendors are adopting a
"standard" of adhering to the recommendations.

;-)

--

Kevin Spencer
Microsoft MVP

Help test our new betas,
DSI PrintManager, Miradyne Component Libraries:
http://www.miradyne.net

"Thomas A. Rowe" <tarowe@xxxxxxxx> wrote in message
news:%23EEXhvCXHHA.4624@xxxxxxxxxxxxxxxxxxxxxxx
There are no HTML standards, just recommendations.

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

http://www.Ecom-Data.com
==============================================


"Murray" <forums@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ej0NHoBXHHA.4240@xxxxxxxxxxxxxxxxxxxxxxx
This does NOT benefit the user. It confuses them. This attitude is
what has gotten IE into the hole it's in now - all this making nice
stuff. There's a perfectly good set of standards out there. They
should not just ignore them willy nilly.

--
Murray
--------------
MVP FrontPage


"Thomas A. Rowe" <tarowe@xxxxxxxx> wrote in message
news:e3r$JCAXHHA.4216@xxxxxxxxxxxxxxxxxxxxxxx
Very simple if the browser can understand what is want or is capable
of display a page when the code is badly written this is a benefit
for the user * of the browser. Browsers that do not do this penalize
users as a way of get back at developers of the site, by making the
site look bad.

* User in this case, are folks that just want to view a web site for
the info it contains, they do not care how the site was coded, etc.

==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

http://www.Ecom-Data.com
==============================================


"P@tty Ayers" <pattyayersTAKETHISOUT@xxxxxxxxxxxxxxx> wrote in
message news:eOIam33WHHA.4180@xxxxxxxxxxxxxxxxxxxxxxx
I guess whether IE's laissez-faire behavior is "wrong" or not could
be debated, but I can't see how you can call it "penalizing" for the
other browsers to interpret code accurately and correctly, Thomas.

--
Patty Ayers | www.WebDevBiz.com
Free Articles on the Business of Web Development
Web Design Contract, Estimate Request Form, Estimate Work***
--


"Thomas A. Rowe" <tarowe@xxxxxxxx> wrote in message
news:uweW2n3WHHA.528@xxxxxxxxxxxxxxxxxxxxxxx
IE doesn't penalized users if the code is wrong, but still
readable, whereas other browsers do.

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

http://www.Ecom-Data.com
==============================================


"Murray" <forums@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Opk1Tq1WHHA.2212@xxxxxxxxxxxxxxxxxxxxxxx
Yep - as Patty notes, IE will forgive you. Other browsers will
not. IE is wrong to do this.

--
Murray
--------------
MVP FrontPage


"Scott" <Scott@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AAD7134C-21ED-4833-BD26-1D1D0C09BFBF@xxxxxxxxxxxxxxxx
Would that make it appear on one computer and not on another - I
would assume
a missing octothorpe would be an all or nothing phenomenon?


"Murray" wrote:

All hex color values MUST be prefixed with the octothorpe "#".
Have you
done this?

#DDDDDD?

--
Murray
--------------
MVP FrontPage


"Scott" <Scott@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F2991032-9D71-47DA-8337-121F8BE9D346@xxxxxxxxxxxxxxxx
I have a frontpage site where I've used hex colors EEEEEE and
F2F2F2 to
display different shades of gray in a table. On my computer,
and most
others, it displays fine. However, I have a client who
apparently can't
display EEEEEE or F2F2F2 (they all look white on her screen).
She can see
DDDDDD (which is almost the same), She has a ATI Radeon
Xpress with Benq
monitor. Is this common? Should I use a different color, or
is it simply
some problem with her setup. Thanks


























.

Loading