Re: [WSG] IE's New JavaScript Blocking Feature

2004-11-27 Thread Mordechai Peller
Derek Featherstone wrote: As for using onkeypress, if the validators (by which I assume you mean Bobby, et al) then, they need to get a clue. The automated tool is only there to help, not to be the final arbiter of what is and isn't accessible. Another solution is not to use in-line JavaScript.

RE: [WSG] IE's New JavaScript Blocking Feature

2004-11-27 Thread JonathanC
I may be missing something here but when WinXP SP2 was installed on all the PCs at work, all it seemed to block were (popup) windows that opened automatically (i.e. onLoad). A link that requires a click, such as: a href=http://google.com/; onclick=window.open(this.href,

Re: [WSG] IE's New JavaScript Blocking Feature

2004-11-27 Thread Patrick H. Lauke
Mordechai Peller wrote: Another solution is not to use in-line JavaScript. Unless they check external script files (which I don't think they do, but I could be wrong) if your script attaches onclick behaviours on load via the DOM, i seriously doubt that bobby will pick this up. to do that, it

Re: [WSG] IE's New JavaScript Blocking Feature

2004-11-26 Thread Mark Harwood
The best and only way i do pop-ups is href=http://google.com/; onclick=window.open(this.href, 'popupwindow', 'width=400,height=300,scrollbars,resizable');return false; this allows you to do whatever you like with the link and also makes it valid, right click-able and so forth.. Remeber to put

RE: [WSG] IE's New JavaScript Blocking Feature

2004-11-26 Thread Derek Featherstone
On Friday, November 26, 2004 2:53 PM, Mark Harwood wrote: The best and only way i do pop-ups is href=http://google.com/; onclick=window.open(this.href, 'popupwindow', 'width=400,height=300,scrollbars,resizable');return false; this allows you to do whatever you like with the link and also

Re: [WSG] IE's New JavaScript Blocking Feature

2004-11-26 Thread Patrick H. Lauke
Mark Harwood Remeber to put onKeypress too I'd disagree. I've had this rant before, but here goes: onclick is not a device specific handler. Onclick is also activated by the keyboard (e.g. hitting return when focus is on a link). It's a misnomer, and should really be onactivation or something.

Re: [WSG] IE's New JavaScript Blocking Feature

2004-11-26 Thread Mark Harwood
OnActivation would proberly be better to use, only reason i state to use onKeyPress is that validators moan if u dont use it. But whatever way you activate the link, this is still the best way to get a pop up or a new page. On Fri, 26 Nov 2004 20:19 , Patrick H. Lauke [EMAIL PROTECTED] sent:

RE: [WSG] IE's New JavaScript Blocking Feature

2004-11-26 Thread Derek Featherstone
On Friday, November 26, 2004 3:57 PM, Mark Harwood wrote: OnActivation would proberly be better to use, only reason i state to use onKeyPress is that validators moan if u dont use it. That's the problem -- there is no onactivate, but that is what they probably should have called onclick though.

RE: [WSG] IE's New JavaScript Blocking Feature

2004-11-26 Thread Mark Harwood
On Fri, 26 Nov 2004 16:05 , Derek Featherstone [EMAIL PROTECTED] sent: My vote: let the automated checkers moan about this all day. Ignore them. Don't add onkeypress in the name of accessibility and device independence... Try telling that to SOCTiM who check all local council sites, they take

RE: [WSG] IE's New JavaScript Blocking Feature

2004-11-26 Thread Mike Pepper
a sequence of tests? Proof of pudding ... Mike -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mark Harwood Sent: 26 November 2004 22:28 To: [EMAIL PROTECTED] Subject: RE: [WSG] IE's New JavaScript Blocking Feature On Fri, 26 Nov 2004 16:05 , Derek Featherstone

Re: [WSG] IE's New JavaScript Blocking Feature

2004-11-26 Thread Patrick H. Lauke
Mike Pepper wrote: Think of onclick as a 2-action process: mouse down selects the object, mouse up - if still on-focus - activates the link, in this instance. Same for keyboard action: tab to object selects it, enter/return activates it. Oh, something just occurred to me: best make it explicit

RE: [WSG] IE's New JavaScript Blocking Feature

2004-11-26 Thread Mike Pepper
Patrick wrote: Oh, something just occurred to me: best make it explicit that we're talking about onclick behaviours on elements that receive focus via the keyboard (links, form elements). obviously, if you have applied onclick to something else (like a plain vanilla image, or a paragraph, etc),

RE: [WSG] IE's New JavaScript Blocking Feature

2004-11-26 Thread Lawrence Carriere
Mark Harwood wrote: --- The best and only way i do pop-ups is href=http://google.com/; onclick=window.open(this.href, 'popupwindow', 'width=400,height=300,scrollbars,resizable');return false; this allows you to do whatever you like with the link and also makes it valid, right