dowload script

[dvsbis]

does anybody have example of file download using
java script

thanks
dave
dv*****@sbcglob al.net

[Evertjan.]

dvsbis wrote on 15 feb 2005 in comp.lang.javas cript:

does anybody have example of file download using
java script

<a href='myFile.tx t'
onclick='alert( "Use rightclick + save target as");return false'>
myFile.txt</a>

--
Evertjan.
The Netherlands.
(Replace all crosses with dots in my emailaddress)

[David Dorward]

Evertjan. wrote:

<a href='myFile.tx t'
onclick='alert( "Use rightclick + save target as");return false'>

Oooh - making assumptions about the user's browser and mouse.

--
David Dorward <http://blog.dorward.me .uk/> <http://dorward.me.uk/>
Home is where the ~/.bashrc is

[Evertjan.]

David Dorward wrote on 15 feb 2005 in comp.lang.javas cript:

Evertjan. wrote:

<a href='myFile.tx t'
onclick='alert( "Use rightclick + save target as");return false'>

Oooh - making assumptions about the user's browser and mouse.

Clientside scripting always does make assumptions.

one-buttoned mouses eh?

--
Evertjan.
The Netherlands.
(Replace all crosses with dots in my emailaddress)

[David Dorward]

Evertjan. wrote:

Clientside scripting always does make assumptions.
No it doesn't - not when you do capability testing with graceful fallback :)

Besides, that wasn't client side scripting, it was system feedback.
one-buttoned mouses eh?

Or no mouse and a keyboard. Or a touch screen. Or ...

--
David Dorward <http://blog.dorward.me .uk/> <http://dorward.me.uk/>
Home is where the ~/.bashrc is

[Simon Wigzell]

"David Dorward" <do*****@yahoo. com> wrote in message
news:cu******** ***********@new s.demon.co.uk.. .

Evertjan. wrote:

Clientside scripting always does make assumptions.

No it doesn't - not when you do capability testing with graceful fallback
:)

Besides, that wasn't client side scripting, it was system feedback.

one-buttoned mouses eh?

Or no mouse and a keyboard. Or a touch screen. Or ...

--
David Dorward <http://blog.dorward.me .uk/> <http://dorward.me.uk/>
Home is where the ~/.bashrc is

My visitor stats inform me that 98.6% of my visitors are running IE or
Netscape on a MS windows system. If any other browser or operating system
visits my site they get a rude noise and a succinct message and get
redirected to http://www.WeAreAllTooPreciousToUseW...eWorldUses.com

[Robert]

In article <sZyQd.403059$X k.26126@pd7tw3n o>,
"Simon Wigzell" <si**********@s haw.ca> wrote:

My visitor stats inform me that 98.6% of my visitors are running IE or
Netscape on a MS windows system.

IE and other browsers can report that they are using any browser the
user wishes. I had to change iCab to say that it was IE on Windows
because some author only allowed IE in his site.

Every hear of Firefox?

Robert

[David Dorward]

Simon Wigzell wrote:

Or no mouse and a keyboard. Or a touch screen. Or ...

My visitor stats inform me that 98.6% of my visitors are running IE or
Netscape on a MS windows system.
What does that have to do with the input device that a user may use (through
choice or otherwise)?
If any other browser or operating system
visits my site they get a rude noise and a succinct message and get
redirected to http://www.WeAreAllTooPreciousToUseW...eWorldUses.com

How sad for you.

--
David Dorward <http://blog.dorward.me .uk/> <http://dorward.me.uk/>
Home is where the ~/.bashrc is

[Evertjan.]

Robert wrote on 16 feb 2005 in comp.lang.javas cript:

IE and other browsers can report that they are using any browser the
user wishes. I had to change iCab to say that it was IE on Windows
because some author only allowed IE in his site.

Personally,
I feel no need to accomodate users that give wrong browser info.

--
Evertjan.
The Netherlands.
(Replace all crosses with dots in my emailaddress)

[Richard Cornford]

Evertjan. wrote:

Robert wrote on 16 feb 2005 in comp.lang.javas cript:

IE and other browsers can report that they are using any
browser the user wishes. I had to change iCab to say that
it was IE on Windows because some author only allowed IE
in his site.

Personally,
I feel no need to accomodate users that give wrong browser info.

The information is only wrong where it is possible to say what would be
right. As the information in question usually originates in the HTTP
User-Agent header it would be the RFC for HTTP that defined what would
be right or wrong in the context of that header, and the HTTP RFCs make
no requirements of the content of the user agent headers. Indeed as the
RFC for HTTP 1.1 was written at a time when the most popular browser
around (IE 4) was itself spoofing by default it was probably not
practical for the authors of the RFC to make any more than suggestions
about its contents.

Richard.