W3C home > Mailing lists > Public > www-style@w3.org > September 2003

RE: Selectors+accessibility (the XML threat)

From: Jörg Hartmann <jhartmann@aquilacoop.de>
Date: Thu, 4 Sep 2003 11:09:10 +0200
To: "'Silas S. Brown'" <ssb22@cam.ac.uk>, "'Jukka K. Korpela'" <jkorpela@cs.tut.fi>
Cc: <www-style@w3.org>
Message-ID: <000e01c372c4$38271df0$6401a8c0@aquila.coop>

Hi,

recommending the use of a programming language for altering CSS on the
client (browser) side is a rather bad idea, among others for security
reasons. (For good reasons JavaScript is simply deactivated in many
corporate environments.) And on the server side it is simply not needed
since you can generate (clean) CSS (and XHTML/HTML) files.

Silas wrote:
> Hi,
> 
> OK, then why not recommend that the user be able to write
> some Javascript (a scripting language that is already common
> in most browsers) that manipulates the properties of the 
> elements before rendering?  Of course, that would mean 
> standardising some way of allowing the script to access the 
> CSS data structures (sort of like DOM but different).
> 
> Best wishes,           Silas
>
> Silas replied to Jukka K. Korpela:
> > What would be needed is a rule that says (globally or for
> > the elements that match a given selector, or set of
> > selectors) "if property P has value X, then use the
> > initial value for P instead, and set property Q to value
> > Y". (This would involve primitive programming, in a sense, 
> and would 
> > take CSS a little closer to a programming language. I don't 
> think this 
> > should be an obstacle, but others might.)
Received on Thursday, 4 September 2003 05:10:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:23 GMT