Tuesday, 20 September 2005 3:04 AM
> To: wsg@webstandardsgroup.org
> Subject: [WSG] Block element inside inline container
>
>
> I would appreciate it if someone could take a look at this
> http://www.earhartrefrig.com/services.htm
> and let me know if I am going to have to
Yes, it's the list changing. I fast fade in would fix it, and if the
client really wants to keep it, then the best thing would probably be
too provide the scripted effect, and let users without script deal with
the harsh version. Tweaking with the appearance of the text might help
too. On 9/19/05,
Christian Montoya wrote:
I think you have to ditch the ul's. By the way, the effect is really
harsh on the yes, maybe it's not the best idea for such large blocks
of text? I didn't even notice the effect right away, because it's not
obvious, but then when I did notice it, it was hard to look at.
That should say "the effect is really harsh on the EYES." whoops. On 9/19/05, Christian Montoya <[EMAIL PROTECTED]
> wrote:I think you have to ditch the ul's. By the way, the effect is really
harsh on the yes, maybe it's not the best idea for such large blocks of
text? I didn't even notice the effe
I think you have to ditch the ul's. By the way, the effect is really
harsh on the yes, maybe it's not the best idea for such large blocks of
text? I didn't even notice the effect right away, because it's not
obvious, but then when I did notice it, it was hard to look at. On 9/19/05, Scott Glasgow <
I would appreciate it if someone could take a look at this
http://www.earhartrefrig.com/services.htm
and let me know if I am going to have to ditch the s. The page HTML and
CSS both validate (4.01 Trans.) except for the the s contained in the
span elements at lines 35, 54, 73, and 89. This is ba
