- From: David Wagner <dwagner@kevric.com>
- Date: Mon, 24 Jan 2000 11:53:51 -0600
- To: "'www-style'" <www-style@w3.org>
A simple way to warn the user of this is to include the warning in an element
normally turned off.
...
.cssmustbeon {display:none; color:red; background-color:yellow;
font-size:gargantuan; blink:madly;}
...
<p class="cssmustbeon">Please fix your silly user stylesheet or thou shalt
become confused mightily by this page. If you have no idea what this message
means, get your sysadmin to fix it for you. Until then, do not fill out this
form. Thanks.</p>
...
Your client-side script may also check the visibility of required form fields,
as well as their content.
Hope this helps. -David
On Monday, January 24, 2000 11:29 AM, Thomas Ashe
[SMTP:Thomas.Ashe@Blackbaud.com] wrote:
> If a user turns off scripting, it is easy enough to detect and alert the
> user that it is required for your application.
>
> If CSS is off, I'm sure that something similar can be done, though I haven't
> tried it specifically. (Turning them on and off is not available in certain
> popular UAs)
>
> But if a user overrides a CSS property...? How can an author detect this? I
> guess one could just set all of the display and visibility in code in the
> onload event. This should override anything set up in stylesheets, but you
> certainly are making the task a lot more difficult and take away the
> "Simplicity, Flexibility,etc..." that the CSS documents extol.
>
> >
> > > If the user adds:
> > > * {display:inline ! important; visibility:visible !important}
> >
> > ...then he will see all the fields, as he probably intended.
Received on Monday, 24 January 2000 12:57:52 UTC