From: "Peter Torr \(MS\)" <ptorr@microsoft.com>
References: <xsS_7.634$X87.83042@news2-win.server.ntlworld.com>
Subject: Re: Inaccessible form submit links in .NET SDK
Date: Wed, 9 Jan 2002 11:03:23 -0800
Lines: 38
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID: <#jmvQBUmBHA.1796@tkmsftngp03>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: tide09.microsoft.com 207.46.137.9
Path: tkmsftngp01!tkmsftngp03
Xref: tkmsftngp01 microsoft.public.dotnet.framework.aspnet:25957

"Tom Gilder" <no@email.ok> wrote in message
news:xsS_7.634$X87.83042@news2-win.server.ntlworld.com...
> The page entitled "Generating Client-Side ECMAScript for Postback"
> instructs users to use a link such as:
>
>   <a id="Link" href="javascript:__doPostBack('Link','')">Link</a>
>
> This type of javascript pseudo-URL's are totally non-standard and
> will only work in browsers that have scripting support, and have
> scripting enabled.

Hi Tom,

In general I agree with you -- the javascript pseudo-protocol is bad -- but
I think the reason they do this is because earlier versions of Navigator
don't support the onclick event for anchor tags (only images, I think) and
so you have to use this hack in order to get Navigator to execute code when
you click a link. If the browser has script disabled, then using onlick
rather than href will not buy you anything, so that point is moot.

Probably the best thing to do for people without script is:

    <a href="?__EVENTTARGET=Link">Link</a>

so perhaps that should be added to the document. I'll send some feedback to
the doc people them with that in mind.

Thanks,

Peter

--
Peter Torr -- ptorr@microsoft.com -- JScript .NET / VSA Runtime
Waiting for the Vengabus? http://www.microsoft.com/info/cpyright.htm
Please post all questions to the group. Thanks.