HEX EEEEEE COLORS WITH IE

S

Scott

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
 
M

Murray

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

#DDDDDD?
 
S

Scott

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?
 
P

P@tty Ayers

It could, because she may be using a different browser, and some are more
"forgiving" of a code mistake than others.
 
M

Murray

Yep - as Patty notes, IE will forgive you. Other browsers will not. IE is
wrong to do this.
 
T

Thomas A. Rowe

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
==============================================
 
P

P@tty Ayers

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.
 
R

Rob Giordano \(Crash\)

I agree with Otto Thorpe whoever he is.



|I have to agree with Patty, no matter how much it pains me.... 8)
|
| --
| Murray
| --------------
| MVP FrontPage
|
|
| | >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 Worksheet
| > --
| >
| >
| > | >> 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
| >> ==============================================
| >>
| >>
| >> | >>> Yep - as Patty notes, IE will forgive you. Other browsers will not.
IE
| >>> is wrong to do this.
| >>>
| >>> --
| >>> Murray
| >>> --------------
| >>> MVP FrontPage
| >>>
| >>>
| >>> | >>>> 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
| >>>>>
| >>>>>
| >>>>> | >>>>> >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
| >>>>>
| >>>>>
| >>>>>
| >>>
| >>>
| >>
| >>
| >
| >
|
|
 
T

Thomas A. Rowe

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
==============================================
 
M

Murray

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.
 
M

Mike Mueller

For the viewing user only, it may lead him/her to think
another browser does not work properly because it does not
render the authors mistakes as the original browser
*guessed* at what the developer intended.

For the looking-for-ideas user, it may lead to a further
propagation of improper coding techniques.

For the original developer who only views his page in one
browser, he/she will be led to believe their coding is OK
and not learn from the mistake they made. This could just go
on and on until the author starts putting in some doc-type
and fails validation when they learn of it and then the
author has multitudes of pages to go through and errors to
fix

Regardless, I think its reaching to say the other browsers
make the sites look bad.

Maybe the browsers' owner could run a bot and look for all
of these codings and extort millions for their big coverup
But in todays legal system, MS would be class-action sued by
the incorrect coders association for teaching them improper
coding techniques. They would also lose then to the other
browsers developers who will state that IE's rendering of
quirk code makes their software look bad


: 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
: ==============================================
:
:
message
: : > Yep - as Patty notes, IE will forgive you. Other
browsers will not. IE is wrong to do this.
: >
: > --
: > Murray
: > --------------
: > MVP FrontPage
: >
: >
message
: >
: >> 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
: >>>
: >>>
message
: >>>
: >>> >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
: >>>
: >>>
: >>>
: >
: >
:
:
 
T

Thomas A. Rowe

Most users will use whatever browser is installed on the machine they are using.

I agree developers need to code pages correctly.

If IE can display the correct color when the # is missing then so can the others.
--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

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

Thomas A. Rowe

There are no HTML standards, just recommendations.

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

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

Mike Mueller

I agree with you on all 3; however, I also agree with Murray
in the fact that just because IE can do it doesn't mean it
should.

What we can all agree on is the problem, but is it an FP
issue at all?



: Most users will use whatever browser is installed on the
machine they are using.
:
: I agree developers need to code pages correctly.
:
: If IE can display the correct color when the # is missing
then so can the others.
: --
: ==============================================
: Thomas A. Rowe
: Microsoft MVP - FrontPage
:
: http://www.Ecom-Data.com
: ==============================================
:
:
: : > For the viewing user only, it may lead him/her to think
: > another browser does not work properly because it does
not
: > render the authors mistakes as the original browser
: > *guessed* at what the developer intended.
: >
: > For the looking-for-ideas user, it may lead to a further
: > propagation of improper coding techniques.
: >
: > For the original developer who only views his page in
one
: > browser, he/she will be led to believe their coding is
OK
: > and not learn from the mistake they made. This could
just go
: > on and on until the author starts putting in some
doc-type
: > and fails validation when they learn of it and then the
: > author has multitudes of pages to go through and errors
to
: > fix
: >
: > Regardless, I think its reaching to say the other
browsers
: > make the sites look bad.
: >
: > Maybe the browsers' owner could run a bot and look for
all
: > of these codings and extort millions for their big
coverup
: > But in todays legal system, MS would be class-action
sued by
: > the incorrect coders association for teaching them
improper
: > coding techniques. They would also lose then to the
other
: > browsers developers who will state that IE's rendering
of
: > quirk code makes their software look bad
: >
: >
: > : > : 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
: > : ==============================================
: > :
: > :
: > message
: > : : > : > Yep - as Patty notes, IE will forgive you. Other
: > browsers will not. IE is wrong to do this.
: > : >
: > : > --
: > : > Murray
: > : > --------------
: > : > MVP FrontPage
: > : >
: > : >
: > message
: > : >
: >
: > : >> 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
: > : >>>
: > : >>>
: > message
: > : >>>
: >
: > : >>> >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
: > : >>>
: > : >>>
: > : >>>
: > : >
: > : >
: > :
: > :
: >
: >
:
:
 
P

P@tty Ayers

Does that mean that it shouldn't be discussed here? I thought that questions
about HTML and browsers were on-topic.
 
M

Mike Mueller

Never claimed it was OT, I was just wondering if any of the
FP versions were responsible for the code.




in message : Does that mean that it shouldn't be discussed here? I
thought that questions
: about HTML and browsers were on-topic.
:
: --
: Patty Ayers | Adobe Community Expert
: www.WebDevBiz.com
: Free Articles on the Business of Web Development
: Web Design Contract, Estimate Request Form, Estimate
Worksheet
: --
:
:
:
: : > No, it is not an FP issue.
: >
: > --
: > ==============================================
: > Thomas A. Rowe
: > Microsoft MVP - FrontPage
: >
: > http://www.Ecom-Data.com
: > ==============================================
: >
: >
: > : >>I agree with you on all 3; however, I also agree with
Murray
: >> in the fact that just because IE can do it doesn't mean
it
: >> should.
: >>
: >> What we can all agree on is the problem, but is it an
FP
: >> issue at all?
: >>
: >>
: >>
: >> : >> : Most users will use whatever browser is installed on
the
: >> machine they are using.
: >> :
: >> : I agree developers need to code pages correctly.
: >> :
: >> : If IE can display the correct color when the # is
missing
: >> then so can the others.
: >> : --
: >> : ==============================================
: >> : Thomas A. Rowe
: >> : Microsoft MVP - FrontPage
: >> :
: >> : http://www.Ecom-Data.com
: >> : ==============================================
: >> :
: >> :
message
: >> : : >> : > For the viewing user only, it may lead him/her to
think
: >> : > another browser does not work properly because it
does
: >> not
: >> : > render the authors mistakes as the original browser
: >> : > *guessed* at what the developer intended.
: >> : >
: >> : > For the looking-for-ideas user, it may lead to a
further
: >> : > propagation of improper coding techniques.
: >> : >
: >> : > For the original developer who only views his page
in
: >> one
: >> : > browser, he/she will be led to believe their coding
is
: >> OK
: >> : > and not learn from the mistake they made. This
could
: >> just go
: >> : > on and on until the author starts putting in some
: >> doc-type
: >> : > and fails validation when they learn of it and then
the
: >> : > author has multitudes of pages to go through and
errors
: >> to
: >> : > fix
: >> : >
: >> : > Regardless, I think its reaching to say the other
: >> browsers
: >> : > make the sites look bad.
: >> : >
: >> : > Maybe the browsers' owner could run a bot and look
for
: >> all
: >> : > of these codings and extort millions for their big
: >> coverup
: >> : > But in todays legal system, MS would be
class-action
: >> sued by
: >> : > the incorrect coders association for teaching them
: >> improper
: >> : > coding techniques. They would also lose then to the
: >> other
: >> : > browsers developers who will state that IE's
rendering
: >> of
: >> : > quirk code makes their software look bad
: >> : >
: >> : >
: >> : > : >> : > : 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
: >> : > : ==============================================
: >> : > :
: >> : > :
in
: >> : > message
: >> : > : : >> : > : > Yep - as Patty notes, IE will forgive you.
Other
: >> : > browsers will not. IE is wrong to do this.
: >> : > : >
: >> : > : > --
: >> : > : > Murray
: >> : > : > --------------
: >> : > : > MVP FrontPage
: >> : > : >
: >> : > : >
in
: >> : > message
: >> : > : >
: >> : >
: >>
: >> : > : >> 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" <[email protected]>
wrote in
: >> : > message
: >> : > : >>>
: >> : >
: >>
: >> : > : >>> >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
: >> : > : >>>
: >> : > : >>>
: >> : > : >>>
: >> : > : >
: >> : > : >
: >> : > :
: >> : > :
: >> : >
: >> : >
: >> :
: >> :
: >>
: >>
: >
: >
:
:
 
M

Murray

Yes, it is. It should be flagged as what it is - invalid HTML. The page
will fail validation.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top