Thanks for all the feedbacks.

My next question is how did they make the message show in certain browsers?
If it is JavaScript or any other scripts, are there any good source for it?
 
With Regards
Jaime Wong
~~~~~~~~~~~~~~~~~~~~~~~~~~
SODesires Design Team
http://www.sodesires.com
~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-------Original Message-------
 
From: [EMAIL PROTECTED]
Date: 03/18/04 07:23:33
To: [EMAIL PROTECTED]
Subject: Re: [WSG] Hiding styles message to certain browsers
 
as well as the media setting for the stylesheet "screen, print, etc"
 
-----
Jeremy Flint
www.jeremyflint.com
 
 
 
Jeremy Flint wrote:
> would it also depend on the method used to include the stylesheet:
> @import vs. link?
>
> russ weakley wrote:
>
>> Nate,
>>
>> First of all, that wasn�t my technique, just the one used by the site
>> mentioned by Jaime.
>>
>> A good articles on hiding content is Joe Clark's:
>> http://www.alistapart.com/articles/fir/
>>
>> This article details the difference between "display: none" and "display:
>> hidden".
>>
>> "It seems clear that any element given a style of display: none should
>> not
>> be rendered, read, or manifested at all by any device in any
>> modality. Hal,
>> IBM Home Page Reader, OutSpoken, and Window-Eyes are behaving properly
>> under this interpretation, while Jaws is misbehaving."
>>
>> Joe Clark's article is referring to hiding heading content, not
>> messages at
>> the top of the page, but the points are still relevant.
>>
>> Russ
>>
>>
>>
>>
>>> There's actually a good reason for this difference. (I can't find the
>>> reference right now, but I think it's in Zeldman's Designing With Web
>>> Standards.) Some screenreaders (Jaws?) observe the display:none CSS
>>> rule, even though it's a visual thing -- therefore, the rule Jeremy
>>> cited won't be accessed in that context, whereas Russ' rule will.
>>>
>>> Neither one is wrong, it's just important to know to whom you're
>>> supplying the message...
>>>
>>> Nate
>>>
>>>
>>> .: Nate Cook : 773 405 4073 : [EMAIL PROTECTED] : www.natecook.com :.
>>>
>>> On Mar 17, 2004, at 8:17 AM, Jeremy Flint wrote:
>>>
>>>
>>>
>>>> you can also use
>>>>
>>>> .hide {
>>>> display: none
>>>> }
>>>>
>>>> <div class="hide">Message to non-stylesheet browsers</div>
>>>>
>>>> russ weakley wrote:
>>>>
>>>>
>>>>
>>>>> These guys use the following CSS rule:
>>>>>
>>>>> .hide {
>>>>> height: 0;
>>>>> width: 0;
>>>>> overflow: hidden;
>>>>> position: absolute;
>>>>> }
>>>>>
>>>>> HTML:
>>>>> <div class="hide">
>>>>> <p>
>>>>> If you are reading this on a mobile device browser or a text browser,
>>>>> you
>>>>> can safely <a href="#maincontent">
>>>>> skip to the content</a>.
>>>>> ...
>>>>>
>>>>>
>>>>>
>>>>> Russ
>>>>>
>>>
>>> *****************************************************
>>> The discussion list for http://webstandardsgroup.org/
>>> See http://webstandardsgroup.org/mail/guidelines.cfm
>>> for some hints on posting to the list & getting help
>>> *****************************************************
>>>
>>
>>
>> Thanks
>> Russ
>>
>> -----------------------------------------------
>> Russ Weakley
>> Max Design
>> Phone: (02) 9410 2521
>> Mobile: 0403 433 980
>> Email: [EMAIL PROTECTED]
>> http://www.maxdesign.com.au
>> -----------------------------------------------
>>
>>
>> *****************************************************
>> The discussion list for http://webstandardsgroup.org/
>> See http://webstandardsgroup.org/mail/guidelines.cfm
>> for some hints on posting to the list & getting help
>> *****************************************************
>>
>>
>>
>>
>>
>
*****************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
*****************************************************

*****************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
***************************************************** 

Reply via email to