Paul Novitski wrote:
> At 10/4/2006 08:49 AM, Thierry Koblentz wrote:
>> I'd appreciate any comment that would help me improve this article:
>>
http://www.tjkdesign.com/articles/the_perfect_image_replacement_technique.asp
>> and http://www.tjkdesign.com/articles/the_perfect_drop_cap.asp

> While of course I agree with the intentions and results of these
> image-replacement techniques, I disagree with one important aspect of
> their implementation: the use of JavaScript.  Using a client-side
> script to modify downloaded HTML is like editing a newspaper after
> the edition has hit the stands.

Hi Paul,

AFAIK, *all* Images Replacement techniques used to use *background* images,
so I'd say it shows that authors never meant these images to be *content*.
IMO, UAs should get the cleanest document possible because we can't assume
who or "what" is the end user (what's the benefit of having machines parse
drop cap images?).
I know PHP is cool (I'm still mad at myself for going with ASP years ago),
but I think the main rule should be to deliver *clean* documents. I believe
the more presentational elements are removed from the markup the better.

> Not to mention, JavaScript-dependent solutions depend, duh, on
> client-side scripting being enabled.  The conscientious developer
> must plan for a scriptless fallback (which you have done
> astutely).

I'm curious to know what would be your approach to create drop caps
server-side. One of the advantages of my solution is that I can rely on the
layers on which the technique is based on to prevent "issues". I can use JS
and CSS to make sure the document always make sense no matter which "layer"
is *off* or even if both are off.
I just can't see how that could be solved through server-side scripting...

---
Regards,
Thierry | www.TJKDesign.com



*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************

Reply via email to