[WEB4LIB] RE: Photos on Home Pages

[Dan Lester]

In IE6.x it is at

Tools | Internet Options | Advanced | Disable Script Debugging

Just check the "disable script debugging" box and you won't be hassled
with those any more.  I've no idea why it is on by default, since the
vast majority of browser users couldn't debug a script if their life
depended on it.

I believe it is in a similar or identical location in IE5.x

dan



Wednesday, December 12, 2001, 11:46:24 AM, you wrote:

BRWL> I haven't followed this discussion closely, but I have a related 
BRWL> question.

BRWL> When MSIE 5.5 can not handle some JavaScript, MSIE offers to 
BRWL> debug the script with Visual Basic. Users at our public workstations 
BRWL> do not know if they should answer yes or no to the dialog. I tell them 
BRWL> to say no. However, if another line of code can not be interpreted, 
BRWL> then MSIE again offers to debug that next line.

BRWL> Is there a way to turn off or deactivate this MSIE behavior. Netscape 
BRWL> 4.7 is very happy to display the same "offending" page without a 
BRWL> similar offer of help. I do not want to disable JavaScript.

BRWL> Thanks, Roy Bennett


BRWL> Date sent:              Wed, 12 Dec 2001 09:54:48 -0800 (PST)
BRWL> From:                   Thomas Dowling <tdowling at ohiolink.edu>
BRWL> Subject:                [WEB4LIB] RE: Photos on Home Pages
BRWL> To:                     Multiple recipients of list <web4lib at webjunction.org>
BRWL> Send reply to:          tdowling at ohiolink.edu

>> At 11:59 AM 12/12/2001, Keith wrote:
>> 
>> >At 11:06 AM 12/12/2001 -0500, I wrote:
>> >
>> >>Any reason why non-Javascript viewers get no picture at all?
>> >>
>> >
>> >It could be that in order to get the starting image to be a random
>> >selection from those available the actual image tag is written by a
>> >script.  Hence, no Javascript == no tag. If you're paying attention,
>> >there's a paragraph missing under the "Did You Know" heading in that
>> >same column. Same reasoning - the paragraph is a random selected
>> >document.write() in a script.
>> 
>> The <noscript> element is the place to put default content to be
>> displayed in place of client side script-generated content.  You could
>> pick one nice image an stick it there.
>> 
>> 
>> >While we're on the no-Javascript issue... I'm guessing you're using
>> >something like Amaya - which doesn't include Javascript support - or
>> >something like it.
>> 
>> No, an obscure little browser called Internet Explorer 6.  I set the
>> Internet Security Zone to disable scripting; when and if a site
>> persuades me that its scripts are worth it, I move it into my Trusted
>> Zone.
>> 
>> Innumerable caveats about methodology aside, pages under 
>> <http://www.thecounter.com/stats/> suggest that more than 10% of users
>> may have client-side scripting disabled.  Users with some vision or
>> cognitive disabilities are also likely to surf with scripting
>> disabled.  Making sure pages work with scripting disabled (and I'm not
>> really arguing that yours is broken) is a priority 1 checkpoint in the
>> Web Content Accessibility Guidelines.
>> 
>> I'll echo Roy's comment that any server-side technology can easily
>> deal out random images minus any client-side hassles.
>> 
>> 
>> Thomas Dowling
>> OhioLINK - Ohio Library and Information Network
>> tdowling at ohiolink.edu
>> 



BRWL> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
BRWL> Roy Bennett
BRWL> Computer Services & Systems Librarian
BRWL> Hamersly Library
BRWL> Western Oregon University
BRWL> 345 N. Monmouth Ave.
BRWL> Monmouth, OR 97361-1396
BRWL> Email:  bennetr at wou.edu
BRWL> Voice:  (503) 838-8893
BRWL> Fax:    (503) 838-8399
BRWL> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@



-- 
Dan Lester, Data Wrangler  dan at RiverOfData.com 208-283-7711
3577 East Pecan, Boise, Idaho  83716-7115 USA
www.riverofdata.com  www.gailndan.com  Stop Global Whining!